Roles and access
See what each organization role can do, and how Screel decides who can open a project.
Organization roles
Section titled “Organization roles”| Capability | Owner | Admin | Member |
|---|---|---|---|
| View members, usage and the audit log | ✓ | ✓ | Own page only |
| Add and remove members | ✓ | ✓ (not the owner or other admins) | No |
| Add an admin | ✓ | No | No |
| Change a member’s role | ✓ | No | No |
| Manage workspaces and their members | ✓ | ✓ | Read only |
| Handle join requests | ✓ | ✓ | No |
| Manage API keys | ✓ | ✓ | No |
| Manage billing and seats | ✓ | No | No |
| Change general settings | ✓ | No | No |
| View the single sign-on configuration | ✓ | No | No |
| Transfer ownership | ✓ | No | No |
| Leave the organization | Transfer first | ✓ | ✓ |
An organization has one owner. You cannot remove the owner, and the owner cannot leave. Transfer ownership in the general settings hands the role to a member who has joined, and the previous owner becomes a member.
Project access
Section titled “Project access”Screel checks these rules and grants the highest level that any of them gives:
- Project creator: full control.
- Organization owner: full control of every organization project.
- Organization admin: edit access to every organization project.
- Explicit share: Edit or View, as shared.
- Workspace member: Edit for editors and View for viewers, on projects in that workspace.
- Any member: View on organization projects in no workspace.
Managing shares needs full control, so the owner can manage shares on any organization project.
Workspace roles
Section titled “Workspace roles”A workspace has two roles: editor and viewer. It has no owner of its own, because organization owners and admins manage workspaces.
