Tutorial Bring your team in safely Step 3 of 12 · Stage 1: Plan who sees what. 0 of 10 steps done Exit tutorial

Super admin vs Administrator

A super admin is an account that skips every permission check. Administrator is a ready-made role with a large but limited set of permissions. Here's how they differ, and which to give.

Why this step

A Super admin: An account that skips every permission check. Keep these to one or two people. skips every check. Giving it out "to save time" is the most common way access goes wrong.

Today you only need:

Applies to
Core 12.0 and later
Who can do this
Platform owner, Administrator

In short

Super admin is a switch on one person's account. Laramin doesn't check any permissions for that person. Administrator is a role, a named set of permissions, that Laramin creates for you. It covers the day-to-day running of the business, but leaves out the powers that could lock people out, rewrite access or destroy data. Most people who run the business should have the Administrator role, not be super admins.

Careful: A super admin skips every permission check. Only make someone a super admin if they will run the whole platform.

How it works

Super adminAdministrator role
What it isThe Super Admin switch on a user accountA role named Administrator
How you give itA super admin turns on Super Admin on the Profile step of the Users formAdd Administrator in the Roles field on the Access step
Permission checksSkipped entirelyLaramin checks every action against the role's permissions
ExperiencesCan enter every experienceGives no experiences. Choose them for each person on the Access step
Workspaces and teamsCan enter every active workspace, and any team in service thereNeeds a membership, like everyone else
Reset or set passwords, sign in as othersYesNo
Delete records forever (….remove) and module bulk-delete permissions (….bulk_delete)YesNo. Ordinary delete and restore are included
Edit roles and permissionsYesNo
Developer and infrastructure settings, addon managementYesNo
Security, Monitoring, Global Search, Public website and Help Center settingsYesNo
Trusted devices audit, account deletion requestsYesNo
Change a record's web address (slug)YesNo

Protections for super admin accounts

  • Only a super admin can see the Super Admin and Allow Impersonation switches, or turn them on or off.
  • Anyone who isn't a super admin can't see super admin accounts. They're missing from the Users list, its counts, search and export. Opening one directly behaves as if the account doesn't exist.
  • Nobody can sign in as a super admin. Nobody can reset or set a super admin's password from the Users screen.
  • You can't remove the last super admin. Laramin says You cannot remove the last remaining super admin.

The Administrator role

Laramin builds the Administrator role from every permission on the installation, minus the powers in the table above. It does this once, when it first creates the role, and never overwrites changes you make to the role afterwards. So permissions that a module adds later, when you install it, aren't added to the Administrator role. Give them to the role yourself. See Change or delete a role.

A module can keep its own sensitive permissions out of the Administrator role. The Administrator role also doesn't include viewing or editing the Experiences screen, because those permissions are in the same group as the experience doors.

Reserved role names

Four role names belong to Core: super.admin, administrator, admin and dev.admin. Nobody but a super admin can create, rename or delete roles with these names. Having the role called super.admin does not make someone a super admin: only the Super Admin switch does.

How it relates to

Next steps

Check it worked

0 of 2 ticked

Tick each one you can see. Ticks stay on this device; they don't stop you moving on.

Check it worked
Back
Steps
Mark done