You will need the Permissions Limited permission to view or change another person's access. It counts at one of that person's profile campuses, meaning the campuses the person belongs to, not their campus limit. Nobody can edit their own access, Super Users included.
Staff access has two layers. Permissions say what someone may do. Limits say where they may do it.
A campus override changes the first layer, permissions, at one campus. Nothing about the campus or organization limit can be changed by an override. Other limits on the permissions screen, such as calendars and note types, belong to the first layer, so an override can change them.
Access types
The Access drop-down on a user offers four choices:
Guest - what members get. New users start as Guests, whether you add them yourself or they register. Guests hold no staff permissions, so this is the right choice for members who are not staff or volunteers.
Super User - every permission at every location, with no limits. See what it still does not bypass, below.
Role Based - whatever the person's roles give. Nothing is stored on the person.
Custom - permissions, limits, field access and overrides stored directly on the person.
Every staff user who is not a Guest can see the church directory, and each profile's privacy settings are always enforced. Staff with permissions also see a link to the Help Center and the support chat. User Access Types explains each access type.
Layer 1: permissions
Permissions decide what someone may do. You set them directly on a person with Custom access, or through roles with Role Based access.
56 permissions are campus-scoped. They can differ from one campus to another, through a campus override.
43 permissions are account-wide. They apply everywhere and cannot be overridden.
Version 8 added two permissions, Bank Reconciliations and Close Accounting Periods. No permission was renamed, removed or split.
Which permissions can differ by campus? lists which permissions are which. How do I set permissions on a user? and How do I set role-based permissions or role-based system access? cover setting them.
Layer 2: limits
Limits decide where someone may work. A limit comes from the Campuses field on a Custom user or a role. Being limited is not one of the four Access choices.
A campus limit names campuses. While multi-campus is on, it binds campus by campus. With more than one organization but multi-campus off, it binds as the whole organizations those campuses belong to. With both off, it does not bind.
An organization limit names whole organizations. It covers every active campus of each one, so a new campus is included automatically.
One limit names campuses or organizations, never both.
How do campus and organization limits work? explains how limits work.
Campus overrides
A campus override is a whole replacement set of permissions for one campus. It changes layer 1 only, never the limit.
Holding any override, even one that only adds access, blocks the actions that reach the whole account: adding an organization, setting the default organization, archiving an organization, moving a campus, the cutover preview, and inviting team members during a trial. What is a campus override? explains overrides in full.
What Super User and Full Account do and do not bypass
"Account-wide admin" is not an access type. When people say it, they usually mean someone with Full Account and no limit. Full Account is one ordinary account-wide permission, and it bypasses nothing.
A Super User still cannot:
Edit their own permissions or revoke their own access.
Read someone else's Only Me notes.
Change a record held only by archived organizations.
Break the rule that a financial record belongs to exactly one organization.
The campus selector still narrows a Super User's lists to what they pick.
A limited Full Account holder cannot change what all organizations share. While your account has more than one organization, anyone with a campus or organization limit sees these screens read-only, even with Full Account: account settings, subscription, payment method, cancellation, billing contact, access approvers, sending domains, texting settings, chat settings, phone numbers, Remote Deposit onboarding and purchases. An override on its own does not cause this.
Access that has nothing to do with limits
Some access comes from a person's relationship to a record, whatever their limit says:
Group administrators see their groups and those groups' child groups.
Members with elevated group settings always see that group, and published groups are always visible.
A current member who holds Full Read Groups sees the group whatever its campuses, within their group type and category limits.
Everyone sees their own profile and household.
Create, edit and delete
Editing a record needs the permission at one of its campuses. Deleting it needs the permission at every one of its campuses. Who can create, edit and delete a record? explains the details.
Helpful Tip
When granting access, review the person's permissions first to make sure they have the access you expect.
