Roles and permissions
The five roles in a RowCall org, what each one can and can't do, and how to choose the right one for each person.
Every member has one role per org. RowCall checks the role on every request, so a person can never do more than their role allows, even by calling the API directly. You can see this table in the app under Settings → Roles.
The roles
| Role | For | Can |
|---|---|---|
| Owner | The person accountable for the org. One per org | Everything, including billing, deleting the org and transferring ownership |
| Admin | Team leads who run the org | Settings, members, invites, flows, calls and developer keys |
| Builder | People who write and test flows | Build, publish and export |
| Operator | Your support or calling team | Start calls, listen in live, take over and transfer calls |
| Viewer | Managers and analysts who only need to look | See calls, flows and results. Changes nothing |
Everything each role can do
| Permission | Owner | Admin | Builder | Operator | Viewer |
|---|---|---|---|---|---|
| See the org and its members | ✓ | ✓ | ✓ | ✓ | ✓ |
| Change org settings | ✓ | ✓ | |||
| Delete the org, transfer ownership | ✓ | ||||
| Invite people, change roles, remove members | ✓ | ✓ | |||
| Read the audit log | ✓ | ✓ | |||
| See flows | ✓ | ✓ | ✓ | ✓ | ✓ |
| Edit and publish flows Preview | ✓ | ✓ | ✓ | ||
| See calls | ✓ | ✓ | ✓ | ✓ | ✓ |
| Start calls, listen in, take over and transfer Preview | ✓ | ✓ | ✓ | ||
| See results | ✓ | ✓ | ✓ | ✓ | ✓ |
| Export results Preview | ✓ | ✓ | ✓ | ||
| Manage API keys and webhooks Preview | ✓ | ✓ | |||
| See the balance, rate, charges and billing activity | ✓ | ✓ | ✓ | ✓ | ✓ |
| Top up, edit billing details, set the low-balance alert, see invoices | ✓ |
Permissions marked Preview are set now and take effect when those features ship.
Rules that always apply
- There is exactly one Owner. Ownership moves only by transfer.
- Admins can't change or remove the Owner, and can't make anyone Owner.
- Anyone can leave an org, except the Owner.
- The app hides what your role can't use. The API refuses it too.
Choosing roles
- Give most people Viewer or Operator. Raise it when they need more.
- Keep Admin to a few people.
- Developers who only set up the integration need Admin for API keys, or ask an Admin to create the key.
See who changed what.