Workspaces & organizations

Organization vs. workspace

Your organization is your company as an account-level entity — the billing relationship and the set of people who belong to it. A workspace is where the work lives: its own agents, knowledge base, integrations, tasks, and credit balance. For most teams there is one organization and one workspace, and the two are effectively the same thing. Larger customers may run more than one workspace under a single organization — for example, to separate two brands or business units.

Seats

A seat is a person who can sign in and work inside a workspace. Your plan determines how many seats you have: Pro includes 3, Growth includes 15, and Scale/Agency plans are sized to you. Adding someone consumes a seat; removing them frees it immediately. Roles (owner/admin/member) control what each seated person can do — see the admin guide for role details and invitations.

Switching between workspaces

If you belong to more than one workspace — say your own company and a client’s — you switch between them from the workspace switcher. Each switch changes your entire context: the agents you see, the integrations available, the knowledge base, and the credit balance all belong to the active workspace. You are only ever operating in one workspace at a time, which keeps it clear whose data and whose spend you are working with.

Data isolation between workspaces

Isolation is not a convenience feature — it is enforced at the database level with row-level security (RLS). Every row of data is scoped to a workspace, and queries are constrained so that one workspace physically cannot read another’s rows.

• Agents, tasks, documents, and knowledge entries belong to exactly one workspace and are invisible to every other tenant.
• Integrations are authorized per workspace; connecting Gmail in one does not expose it to another.
• Credits and billing are per workspace, so spend never bleeds across tenants.
• Members only see the workspaces they have been invited to.