Workspace Guide
Workspace access
How workspace membership, active context, and MCP access fit together.
Every MCP session runs against one active workspace. That workspace decides which generations, balance, members, and settings the assistant can access.
If your account belongs to multiple workspaces, the assistant should list or switch workspaces before taking an action that affects billing, team members, or stored generations.
Access rules
Only members of a workspace can view its generations, balance, and team state.
Owners can manage billing, settings, invitations, and destructive workspace actions.
Members can run supported day-to-day actions inside the workspace but cannot change ownership-level settings.
Role capabilities
| Capability | Owner | Member |
|---|---|---|
| Generate images, video, audio | Yes | Yes |
| View workspace generations | Yes | Yes |
| Check balance | Yes | Yes |
| Invite team members | Yes | No |
| Top up workspace balance | Yes | No |
| Rename or delete workspace | Yes | No |
| Create / revoke API keys | Yes | No |
Recommended assistant flow
When a user says "use the Acme workspace" or "invite someone to marketing," the assistant should first confirm or switch the active workspace, then run the relevant team or generation tool inside that context.