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. Learn how to set permissions on a user.
There are four access types to choose from.
Guest
Guests have the least amount of access to the system. They do not have access to view any people data, and if it is granted, it is limited to active profiles only. They can only view "public" areas of the system such as groups, events, forms, and sermons. They can also view and edit general and contact information on their own profile, and they can view their giving history and important dates.
When Guest is selected, no other security setting is used. This is the default access granted when someone registers for system access from the login screen.
Super User
Super users have unrestricted access to the system. This includes account subscription, billing, and financial data.
There must always be at least one super user in the system, 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. Select the roles you want and all permissions across those roles are applied to the user together.
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 list of roles themselves, go to Settings & Tools > Security > Roles.
Custom
Custom access lets you define permissions for one person only, without using a role. Choose this 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 directly on the user.
Which permissions can I set?
Whether you're 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: