Workspaces
What a workspace holds, and when to use more than one.
A workspace is where the work lives. It holds your automations, the connections they use, and the history of every run.
Your organisation is the account above it — it owns the subscription and the people. Workspaces sit inside it.
What a workspace contains
| Automations | The workflows you build, and the folders you organise them in |
| Connections | One per integration — your authorised link to each tool |
| Run history | The record of every execution, retained per your plan |
| Members | The people invited to this workspace |
The important one is connections. A workspace holds a single connection per integration, so it's effectively one set of credentials and the automations that use them. One workspace means one WordPress site, one Notion account, one mailing list.
That constraint is what makes a workspace a meaningful boundary rather than just a folder.
When one is enough
A single business running its own site needs one workspace. Everything shares the same accounts, so there's nothing to separate.
When to use more than one
Reach for a second workspace when you need different credentials for a different context:
An agency with several clients. Each client's site, mailing list and CRM are separate accounts. A workspace per client keeps them apart, and — because membership is per workspace — lets you give a contractor access to one client without exposing the rest.
Several of your own sites. Each site needs its own WordPress connection, so each needs its own workspace.
Staging separated from production. Keeps test automations and test connections away from live ones.
What doesn't cross between workspaces
Nothing, by default. Automations only see the connections in their own workspace, and run history is per workspace.
The one exception is a sub-automation call into another workspace, which needs a plan including cross-site automation. That's how a single workflow can span sites — and the child run belongs to the workspace it ran in, not the one that called it.
How many can I have?
The number of workspaces depends on your plan. See Plans and actions.
Access is per workspace
Being in your organisation doesn't grant access to everything in it. People are invited to a specific workspace and see only that one.
A member of a workspace can build automations there, which means using its connections — acting through your connected accounts without ever seeing the credentials. Choose which workspaces someone joins with that in mind. See Inviting your team.
Choosing a structure
Two questions usually settle it:
- Do these workflows use the same accounts? Different accounts for the same tool means different workspaces — there's no way around it, since a workspace holds one connection per integration.
- Should the same people see all of this? If not, split. Access is granted per workspace, so it's the only boundary available.
If both answers point to "same", keep it in one workspace. Splitting for tidiness alone means reconnecting the same tools twice and looking in two places for run history.
