Spaces, teams and members

When you run several businesses, clients, or projects, cramming everything into one workspace turns into chaos — mixed files, mixed budgets, mixed permissions. Spaces keep each one cleanly separated, so every venture is its own company with its own people, agents, and resources.

The hierarchy

User                 ← you, across every company you belong to
 └─ Space            ← one company / workspace
     ├─ Members      ← people, each with a role
     ├─ Teams        ← groups of agents + people for a function
     └─ Agents       ← the AI workforce

• User — your single account. You can belong to and switch between many Spaces.
• Space — a company: members, roles, billing, shared Drive, and shared credits live here. This is the collaboration boundary.
• Team — an optional grouping inside a Space that bundles agents and the people who work with them around a function (support, marketing, ops).
• Agent — the AI worker that does the job. See agents and Claws.

Spaces are companies

Treat each Space as a separate company. If you serve multiple clients or run multiple ventures, give each its own Space:

Space A: Your own company
Space B: Client A's project
Space C: Client B's project

People, files, agents, budgets, and permissions stay cleanly separated. You switch between them from the workspace switcher — see switch spaces.

Members and roles

Invite teammates into a Space and assign each a role that controls what they can see and do. Roles govern access to agents, Drive, billing, and settings. For the full breakdown, see roles and permissions and invite members.

What's shared inside a Space

Everything in a Space is shared by its members, within their roles:

• Agents and their work
• Shared Drive — a Space-level knowledge base agents and people can read and write
• Credits — a single credit pool all agents draw from
• Space-scoped Skills and Automations
• Channels, connectors, and settings

Related