Skip to content
Sign up freeSign in

Admin roles and permissions

Two layers decide who can do what in an organization:

  1. Organization roles — every member has exactly one: Owner, Admin, Member or Auditor. They're set when you invite someone and changed by the Owner in the member list.
  2. Admin roles — narrower bundles the Owner can hand to individual members on top of their organization role, so someone can look after the domain, say, without being able to remove members.

Whatever the role: no role can ever read anyone's mail. Administration means members, addresses, mailboxes, domains and settings — never message content. The console says so where the roles are assigned: "Admin roles grant administration only — no role can ever read anyone's mail."

Organization roles

RoleWhat they can do
OwnerEverything. The Owner is the organization's super admin: the only one who changes members' roles, assigns admin roles, resets another admin's sign-in security, and can delete the organization.
AdminRuns the organization day to day: invites, members, company mailboxes and addresses, domains, mail settings, the audit log. Can reset sign-in security for members who aren't admins.
MemberA regular colleague — the default when you invite. Uses their company mailbox; no administration.
AuditorRead-only: sees the member list and member details, the domain setup, and the audit log. No management actions.

The console header shows your own standing — for example "Owner · Super admin".

Owner can't be invited directly. An existing Owner promotes a member to Owner from the Role select in the member list, and an organization always keeps at least one Owner — the last one can't be demoted or removed.

Admin roles (delegated)

The "Admin roles" section of the console — visible to the Owner only — lists four roles, shows what each grants, and lets the Owner assign them: pick a Member and a Role, then "Assign role". "Remove" → "Remove role" takes one away: "They immediately lose that role's admin abilities. Their mailbox and mail are untouched." A member can hold several.

Admin roleWhat it grants
User management adminThe whole member-administration area: View member details, Reset sign-in security, and Manage member addresses (company mailboxes and aliases). New member-management abilities land with this role automatically as the product grows.
Help desk adminView member details and Reset sign-in security — exactly today's support abilities, nothing that grows.
AuditorView member details and Read the audit log.
Domains adminDomain administration: View domains and Manage domains — add, verify, check, suspend, resume, remove, send the test message.

The permissions themselves, in the words the console uses when something is out of reach ("You need the "Manage domains" permission for this."):

PermissionLets you…
View member detailsOpen a member's details: their company mailbox's storage use and status, app-password and session counts. Never message content.
Reset sign-in security"Revoke app passwords" and "Force sign-out" on a member's company mailbox.
Manage member addressesGive members company addresses (which creates their mailbox), add aliases, and suspend, restore, transfer, forward and delete company mailboxes.
View domainsSee the Domains section and its checks.
Manage domainsEverything under Domains.
Manage organization mail settingsThe "Trust teammate mail" setting.
Read the audit logThe Audit log section.
Manage admin rolesAssign and remove admin roles — the Owner only; it's never part of a role.

How the organization roles map onto the same permissions: the Owner holds all of them; an Admin holds all but Manage admin roles; an Auditor holds View member details, View domains and Read the audit log; a Member holds none.

The admin-versus-admin boundary

Resetting sign-in security on a protected member — an Owner, an Admin, or anyone holding an admin role — is reserved for the Owner. Everyone else sees the buttons disabled with "Only the organization owner can reset another admin". The same goes for changing roles and assigning admin roles: super admin only, whatever other roles someone holds.

The audit log

Every privileged action is written to the organization's Audit log (needs Read the audit log): who did what, to whom, and when — newest first, with "Load more" for history. Entries read as sentences, for example:

Members see the other half of the same picture in their own Mail settings: what the organization's admins can do (see storage use, reset sign-in security) and can never do (read their mail), plus whether colleague mail skips the Screener.

Last updated: 2026-09-11

Related articles