Every user in the system is given one Access type, and that choice decides how the rest of their permissions work. To set it, go to Settings & Tools (Cog icon in the tool-bar) > Security > Users, open the three-dot menu beside a person, and choose Manage permissions. How do I set permissions on a user? walks through the steps.
There are four access types to choose from: Guest, Super User, Role Based and Custom.
Note: Being limited to campuses or organizations is not one of the four access types. A limit comes from the Campuses field on a Custom user or on a role. Security Overview explains how permissions and limits fit together.
Guest
Guests have the least access to the system. Guest is what members get, and it is the default when someone registers for access from the login screen.
A Guest holds no staff permission and never has campus overrides.
Guests can view public areas such as groups, events, forms and sermons. They can view and edit the general and contact information on their own profile, and view their giving history and important dates.
The only extra thing a Guest can hold is the hidden directory permission, and only when directory access allows it and the person is verified. Directory access only ever shows active profiles.
Whether a Guest can view the people directory depends on their Can view people directory setting:
Always and Never decide on their own.
Use global setting follows the directory setting of the Guest's organization. Set individually there means no, all guests means yes, and custom criteria means yes if the Guest matches.
Super User
A Super User gets every permission at every location, with no limits and no campus overrides. That includes account subscription, billing and financial data.
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, or break the rule that a financial record belongs to exactly one organization. The campus selector still narrows their lists.
Only a Super User can make someone a Super User, edit a Super User's access, or revoke it.
There must always be at least one Super User, so the software will not allow all of them to be deleted.
When a Super User is deleted, their search queries, email templates and resource requests are reassigned to the Super User deleting the profile.
Role Based
Role Based access builds a user's permissions out of one or more saved roles. The person stores only a list of roles, and the roles are read live, so a change to a role reaches everyone who holds it.
Warning: Saving someone as Role Based wipes the permissions, limits, field access and campus overrides stored directly on them. After that, overrides come only from their roles, and Add campus override is hidden for that person.
With several roles, permissions add up, and custom field access takes the highest.
A campus limit holds only if every role has one, and their campuses add up. One role with no limit removes the limit entirely.
The Role Based choice is what counts, not the roles listed. A person marked Role Based with no roles has no permissions and no limit. A person not marked Role Based ignores any leftover roles.
The permission tree shown underneath is read-only for this access type, because it is the combined result of the selected roles. To manage the roles themselves, go to Settings & Tools > Security > Roles. How do I set role-based permissions or role-based system access? covers setting them up.
Custom
Custom access stores permissions, limits, field access and campus overrides directly on one person, without using a role. Choose it when someone needs a combination of access that no role covers. The permission tree becomes editable, and you set each permission, campus and custom field on the user.
Rules that apply to every access type
Every staff user who is not a Guest holds the hidden people directory permission.
Switching someone to Guest removes their permissions, roles, campus limit, organization limit and overrides.
Nobody can edit their own access, Super Users included.
Without Permissions Full, you cannot switch someone who holds a financial permission to Guest or Role Based, or give or take away a role that holds one.
A archived profile cannot use the system. The person sees User account has been deactivated.
Which permissions can I set?
Whether you are building a role or setting custom access for one person, the permissions themselves are the same. Each group has its own article in this collection:
Which permissions can differ by campus? shows which permissions can be changed at one campus, What is a campus override? explains how that works, and Campuses and organizations in Version 8 explains how campus access works.

