Workspaces
The boundary everything sits inside, when to open a second one, and what does not cross between them.
A workspace holds agents, boards, connections and people. It is the unit of isolation: two workspaces share nothing by default, cannot see each other’s items, and do not pool credits from workspace settings. If you have ever asked “should this be one workspace or two”, the answer is one, unless the two halves genuinely must not see each other’s orders.
When a second workspace is right
- Two businesses with separate books, separate suppliers and separate staff.
- A client-services arrangement where each client’s data must stay apart.
- A sandbox you are willing to break, kept away from the one that answers real customers.
When it is wrong
- Separating by channel. One workspace with several connections handles Etsy and Shopify together, and an order that came from one and ships against stock counted in the other is a single item, not two.
- Separating by team. That is what roles are for.
- Separating by season or campaign. Boards and filters handle that, and a workspace you abandon in February still holds its connections.
What crosses a workspace boundary
| Thing | Crosses? | Notes |
|---|---|---|
| Your sign-in | Yes | One account, many workspaces. You switch without signing in again. |
| Personal credit balance | Yes | Balances are account-scoped, not workspace-scoped. |
| Provider connections | Partly | Authorised once against the account, then selected per workspace. The credential is not copied into the workspace. |
| Agents | No | An agent belongs to one workspace and is not visible from another. |
| Boards and items | No | Never visible across a boundary. |
| Run history | No | Stays with the workspace the run happened in. |
| A handoff | Only explicitly | Cross-workspace delegation is a separate, deliberate arrangement and never implicit. |