Getting started
Teams and roles
Simulations, keys and billing belong to an organisation. People join an organisation with a role, and the same rules apply in the dashboard, the management API and the MCP server.
Organisations
Everyone gets an organisation of their own when they sign up, named after their company. Everything you create lives there: simulations, forks, snapshots, rules, webhooks, simulation keys, account keys, the subscription, the AI allowance and prepaid credit. If you belong to more than one organisation, switch between them with the organisation menu at the top of the sidebar.
Roles
| Owner | Admin | Developer | Viewer | |
|---|---|---|---|---|
| See simulations, data, logs and activity | Yes | Yes | Yes | Yes |
| See the team | Yes | Yes | Yes | Yes |
| Create, change and delete simulations, rules, webhooks, forks and snapshots | Yes | Yes | Yes | - |
| Create simulation keys | Yes | Yes | Yes | - |
| Create account keys for yourself | Yes | Yes | Yes | - |
| See and revoke everyone's account keys | Yes | Yes | - | - |
| Invite, remove and change the role of members | Yes | Yes | - | - |
| See and manage billing | Yes | Yes | - | - |
| Transfer ownership, delete the organisation | Yes | - | - | - |
- There is exactly one owner. The owner cannot leave or be removed; they transfer ownership to another member first, and become an admin.
- Nobody can change their own role. Admins cannot change or remove the owner.
- Viewers cannot create or reveal keys. Keys are only ever shown once, when they are created.
- Admins act for the organisation: what they do, including changes to billing, is done on the organisation's behalf.
Invitations
Owners and admins invite people by email from the Team page, choosing their role. The invitation link is valid for 7 days and only works for the address it was sent to. Someone without a Slurry account creates one with that address and joins as soon as they confirm it. Resending an invitation sends a fresh link and the old one stops working; revoking it frees the seat.
Seats
| Plan | Seats |
|---|---|
| Starter | 1 (just the owner) |
| Team | Up to 10 |
| Scale | Up to 50 |
Seats are members plus pending invitations. An organisation without an active plan has one seat. To downgrade to a plan with fewer seats, remove members or revoke invitations first.
Account keys and the API
An account key (slurry_acct_...) belongs to the organisation and to the member who created it, and acts with that member's current role, never more. If the member is removed, leaves, or is downgraded below what the key needs (a read and write key needs developer or above), the key stops working on the next request with 403 member_access_revoked. A read-only key always acts as a viewer. Calls that the role does not allow return 403 forbidden, in the API and as MCP tool errors.
Billing and usage
The subscription, the monthly AI allowance, prepaid credit, your own model key and the request quota are shared by the whole organisation. AI generation started by any member draws on the organisation's allowance.
Who can see what
Members of an organisation can see each other's names and email addresses, and the audit trail records who changed what. Owners and admins can see pending invitations and the email addresses they were sent to.