Workspaces
An account can hold several isolated workspaces - each with its own runs, events, keys, and runners - shared by members and metered against one pooled allowance.
A workspace is an isolated slice of Duraton: its own runs, events, API keys, runners, and webhooks. Nothing crosses between workspaces - an event, run, or key in one is invisible to every other.
Your account starts with one workspace and can hold several. Use one per product, per environment (staging vs production), or per team - whatever boundary you want kept fully separate.
Switching workspace
The console acts on one active workspace at a time. Switch it from the account menu; every view - runs, events, keys, usage - follows the switch. The engine URL and API keys are per workspace, so a runner authenticates against exactly one.
Members and roles
Invite people to your account and give each a role. The role sets what they can do:
| Role | Can |
|---|---|
| Owner | Full control of the account, including other owners and deleting it. |
| Admin | Manage workspaces and members, and read + write across every workspace. |
| Member | Read across the account's workspaces; write is granted per workspace. |
Usage and limits
Usage - steps, events, and the rest - is metered per workspace but pools across your account:
every workspace draws from one shared plan allowance. Reach the limit and the account's workspaces
stop starting new runs until usage resets at the start of the next period. In-flight waiters still
wake; only new runs are refused (a triggered event reports suspended).