Organisations, Roles and Seats
Who can do what in a SynapseOrch Cloud organisation, and which roles count toward a plan's builders and seats.
Everything on SynapseOrch Cloud belongs to an organisation: agents, workflows, tools, runs, usage and billing. People are members of it, each with one role.
The four roles
Roles are ordered — each includes everything below it.
| Role | Can |
|---|---|
| Viewer | Read everything — workflows, runs, results — and change nothing. A viewer cannot start a run, chat, or answer a run or an approval |
| Approver | Everything a viewer can, plus answer a run waiting for a person and a tool call waiting for approval. Free on every plan, like a viewer |
| Builder | Everything an approver can, plus create and edit agents, workflows, tools and schedules, start runs and chat |
| Admin | Everything a builder can, plus invite and remove members and change their roles, create API keys, add provider keys, manage the plan and billing, rename the organisation, and set who is notified of what |
| Owner | Everything, plus making, changing or removing owners, and clearing the organisation's data |
Knowledge. Everyone in the workspace reads knowledge bases and can run a base's test search. Builders create and change bases, their documents and records, and webhook endpoints. Admins also choose the workspace's Knowledge models and save rerank keys.
Owner exists separately from admin on purpose: an organisation needs a holder that an admin they invited cannot remove. Only an owner can invite someone as an owner, change an owner's role or remove one, and the last owner cannot be removed.
The person who creates an organisation is its owner. To close an organisation, an owner asks us — see Deletion.
Seats
Anyone who can create or edit — builders, admins and owners — counts toward the plan's builders, and on a paid plan each one takes a builder seat. Viewers count toward neither, on any plan, however many there are.
That distinction is the one to plan around: an organisation where four people build and twenty read results needs four builders, not twenty-four. Give people viewer unless they actually author.
Each plan has a ceiling on builders: 2 on Free, then 10, 25 and 100 (see Plans and credits). A paid plan includes some seats and adds more at a fixed per-seat price up to that ceiling; when you add one, the charge is shown and confirmed before it is applied. Settings → Members says how many people can build, of how many the plan allows.
- Invitations count while pending. An invitation as builder, admin or owner holds its place until it is accepted, revoked or expires. An expired one holds no place, and on a paid plan a seat bought for it drops off at the next renewal. Resend an expired one and it asks for its place again — and, past the included seats, for the seat, with the charge shown first. An invitation as viewer is never refused.
- Promoting a viewer at the ceiling is refused, with the way out: The Free plan includes 2 people who can build, and this workspace already has 2, counting pending invitations. Make someone else a viewer first, or upgrade.
- Making someone a viewer frees a place at once. On a paid plan, a seat bought beyond the included ones drops off at the next renewal.
Inviting people
Admins and owners invite by email under Settings → Members (Invite someone). An invitation carries the role you choose, and you can change a member's role afterwards. Only an owner can invite an owner. An invitation expires after seven days; Resend sends a fresh link with seven more. Inviting an address whose invitation has expired says so — The invitation to … has expired. Resend it, or revoke it and invite them again.
Someone invited to an organisation who already has a SynapseOrch account joins it directly; someone new creates an account first.
More than one organisation
A person can belong to several organisations. Switch workspace, in the workspace menu and the account menu, lists them; choosing one signs you into that organisation at its own address. Nothing is shared across them — separate workflows, separate runs, separate billing. Use that for a genuine separation such as a client boundary, rather than for organising your own work, which is what folders and naming are for.