Sayli has four roles. They are simple on purpose, so there is never a question about who can do what.
| Role | Can | Cannot |
|---|---|---|
| Owner | Everything an Admin can, plus the plan: buy, change, pause or cancel it, and see invoices and payment details. Make someone else an Owner | Leave while they are the only Owner and others remain |
| Admin | Invite and remove people, set roles up to Admin, change workspace settings such as transcript retention and public links, manage webhooks, read the audit log and team analytics | Change the plan or see invoices, or make someone an Owner |
| Member | Record calls and use every feature, add to the shared Knowledge Base, and connect the workspace's tools | Manage people, workspace settings, webhooks, or the audit log |
| Viewer | Read what they are allowed to see. Viewers are free and take no seat | Record a call, upload, edit a brief, or change anything |
Two rules worth knowing
A webhook only ever delivers what the person who created it can read. Webhooks are an admin resource, and a meeting-bound event reaches an endpoint only if that endpoint's creator can see the meeting. If the admin who set a webhook up leaves the organization, the endpoint goes quiet until another admin recreates it. That is deliberate: an endpoint with no living owner in the org would otherwise keep sending briefs to a URL nobody is accountable for.
Access ends when membership ends. Removing someone closes their live sessions immediately. Their export stops at the workspaces they still belong to, and a call they recorded for your organization stays your organization's record.
The last Owner
An organization always needs an Owner, so Sayli refuses to remove the last one. If you are the only Owner, you cannot demote or delete yourself until you have made someone else an Owner first. It is a small guardrail that keeps an org from locking itself out.