Running several workspaces
What is shared, what is not, and how cross-workspace delegation differs from both.
Most operations need one. Several make sense when two businesses genuinely must not see each other's orders, when a client-services arrangement requires each client kept apart, or when you want a workspace you are willing to break.
Switching
One account, many workspaces, no second sign-in. Your credit balance is account-scoped and follows you; boards, items, agents and run history do not, and are never visible across a boundary.
Cross-workspace delegation
Work can be handed between workspaces, and it is always an explicit arrangement rather than something that happens because two workspaces share an owner. Without one, an agent cannot see anything outside its own workspace, let alone hand to it. This is the mechanism behind agent-to-agent handoffs across a boundary and it is deliberately not implicit.
| Same workspace | Across workspaces | |
|---|---|---|
| Agent sees the item | Yes, if briefed for it | Only through an explicit delegation |
| Trace stays continuous | Yes | Yes, across the delegation |
| Connections shared | Yes, once selected | No — each workspace selects its own |
| Members shared | No | No |