Skip to content

Roles and permissions

Every member of an organization has one role. The role is checked on every request, so a change takes effect at once.

OwnerAdminViewer
See the overview, violations, creatives, policies, Playground results and incidentsYesYesYes
See the list of membersYesYesYes
Write and save policies, upload images to the Policy Playground, run testsYesYesNo
Confirm violations or mark false positivesYesYesNo
Update incidents (status and notes)YesYesNo
Create apps, create and revoke upload keys and API keysYesYesNo
Manage notifications (e-mail and webhook subscriptions, delivery log)YesYesNo
See and manage invitations, read the audit logYesYesNo
Invite a viewer or an adminYesYesNo
Invite an ownerYesNoNo
Change a member between admin and viewerYesYesNo
Make someone owner, or change an owner’s roleYesNoNo
Remove an admin or a viewerYesYesNo
Remove an ownerYesNoNo

The dashboard sums it up as: “Owner: everything, including owners. Admin: everything except owners; can change admin and viewer roles. Viewer: read only.”

  • Admins never touch owners. An admin cannot change an owner’s role, cannot make anyone owner, cannot remove an owner and cannot invite or re-invite an owner. Admins can change their own role between admin and viewer, and can remove themselves.
  • There is always an owner. The last owner cannot be demoted or removed. Make someone else owner first.
  • Invitations follow the inviter. If a member loses the right to grant a role (for example an admin becomes a viewer), the pending invitations they can no longer grant are revoked.
  • Removal is immediate. A removed member is signed out of the organization at once. Being invited again later does not bring back an old session.
  • API keys are not members. Requests made with an API key are limited by the key’s scopes, not by a role, and cannot manage members or invitations. See Authentication.