Workspace

A workspace is your tenant: the boundary within which all your data, agents, integrations and knowledge live — and outside of which none of it is visible.

Isolation guarantee

Every row, every cell, every asset, every run belongs to exactly one workspace. No workspace sees another’s leads, replies, knowledge, or costs — not even through shared integrations or providers running behind the scenes. This separation is not a convention, it is enforced: new code cannot write a query that bypasses this boundary.

One exception, deliberate and narrowly scoped: the Pool, a platform-wide reservoir of raw company/lead candidates (a sourcing reservoir). Pulling from the Pool into a workspace is always a copy, never a reference — once a record sits in your workspace, it belongs exclusively to you.

Members and permissions

A workspace has multiple members with different roles. Structure-changing approvals (a new table structure, new columns, playbook changes) require administrator rights in the workspace; operational approvals (approving a single run) are open to further members depending on their role.

What lives in the workspace

Your workspace is the frame for everything else in this handbook: Knowledge (assets and learnings), Tables with their rows, Playbooks, Integrations, Agents, and the Runs they produce. None of it exists outside a workspace — there is no platform-wide view into your business data.