Roles, access, and security
Requesting and approving access changes
Access-change guidance should keep requesters, approvers, and sensitive follow-up paths explicit so permissions do not drift by assumption.
Who this is for: Church admins, staff leads, and anyone coordinating access changes.
Last reviewed 2026-04-30 · Source of truth: broader help library · Languages: en, es
Article metadata
Product area: access and security
Owner: Auth and permissions
Parity reviewer: Bilingual launch review
Retrieval-ready: Yes
What to expect next
- Name the requester, the church-side approver, and the exact access concern before asking for help.
- Escalate when the change touches identity, financial visibility, or broad admin powers.
Who should ask and who should confirm
The person requesting an access change should be identifiable, and the church-side approver should be clear when the change affects real permissions or sensitive records.
Do not treat informal hallway approval or vague team memory as enough for consequence-heavy access changes.
What support should not guess
Support-facing surfaces should not guess whether a requester is authorized to add, remove, or broaden access for someone else.
When identity, authority, or scope feels unclear, narrower verification and escalation should win over speed.
Escalation path
If the access request could affect sensitive records, financial visibility, or admin-level control, use structured intake and explicit approval rather than conversational guesswork.