Review Role Permissions

Role permissions control which pages people can open and what they can do there. A page can be visible while its editing controls remain unavailable. Review access against the person's responsibilities and campus.

Review and save a role

1. In the web app, open Church Admin, then Role Permissions or Manage RBAC.
2. Choose the role under Select Role to Configure. If the screen says Select Role to View or View only, your account can inspect permissions but cannot save changes.
3. Review each relevant category. Keep Default to use the standard grant, or choose Enabled or Disabled for a church-specific override.
4. Select Save Changes. Have an affected member refresh and verify the intended workflow in the correct church and campus.
5. Use Reset to Defaults only when you intend to remove the selected role's custom overrides.

A role change applies to members with that role. Church Admin access can be granted separately from an operational role. It does not transfer church ownership, and changing a primary contact does not grant account access.

Separate viewing from taking action

• Dashboard and Attendance have their own viewing permissions.
• Church Admin overview access does not automatically grant every administration section. Scheduling Options, News Feed Settings, Role Permissions, Planning Center, Branding, File Manager, Billing, Team Activity and Audit Log each have a view permission. Changing settings still needs the relevant management authority.
• Schedules separates View Schedules, Create Schedules, Edit Schedules, Participate in Assigned Shifts and Volunteer For Schedules. Manage Scheduling Options and Manage Service Times are separate administration controls.
• Checklists separates View Checklists, Complete Checklists, Manage Checklists and Delete Checklists. Complete Checklists covers starting and editing runs, completing them and uploading photos; Manage Checklists covers templates.
• Equipment separates viewing, adding, editing, deleting, Checkout Equipment and Check In Equipment. Viewing or checkout permission alone does not authorize returns.
• Chat separates View Chat from Participate in Chat. Delete Any Chat Message is a separate moderation permission under Communications.
• Communications separates View Team Notices from Manage Messages, which controls authoring notices.
• Trainings & Certifications separates viewing, Respond to Training Invitations, Manage Readiness Records and Manage Readiness Requirements. RSVP correction authority also depends on the attendee and leader's campus scope.
• Campus Maps separates View Campus Maps from Manage Campus Maps. Point visibility can further limit what a reader sees.
• BOLO Alerts separates View BOLO Alerts, Manage BOLO Alerts and Archive BOLOs. A BOLO's selected audience can restrict access further.

Review sensitive and administrative actions

Incidents has separate create, edit, delete, archive, general viewing and sensitive-record viewing controls. Sensitive and archived records retain additional visibility restrictions. A notification or shared link does not bypass them.

Team controls cover viewing, invitations, profile edits and removal. Campus controls cover viewing and editing campuses, managing areas and assigning members. Procedures has separate viewing and upload permissions. Settings and Manage Users provide broader administration; grant them only for responsibilities that require them.

Password recovery is handled through sign-in and its recovery flow. Reset Passwords is no longer a church RBAC control. Do not ask a member to send you their password, authenticator code or backup code.

Limits that a permission switch does not override

The church must have the feature available, and the member must have access to the relevant campus and record. Read-only billing state, Planning Center ownership and a record's lifecycle can also prevent changes.

Map management remains limited to Church Admins, Directors of Safety and Security and Campus Security Leads with the required grant. Incident and BOLO archives are visible only to eligible leadership roles: Church Admins, Directors, Campus Security Leads and Pastoral & Ministry Staff. Enabling a switch for another role does not remove those restrictions.

Pastoral & Ministry Staff can have incident, training and scheduling management access while remaining read-only for operational checklist, equipment and chat actions by default. This role is excluded from security-service assignments and volunteering even when separate Church Admin access is present.

When an action is unexpectedly unavailable, ask an administrator to check the specific permission, church, campus and record. Avoid enabling unrelated permissions to work around an error.