Roles, access, and security
Sensitive access and identity escalation rules
Identity and permissions edge cases should route into narrower, reviewable handling instead of relying on reassurance or guessed authority.
Who this is for: Admins and staff facing high-trust access, identity, or permissions uncertainty.
Last reviewed 2026-04-30 · Source of truth: broader help library · Languages: en, es
Cases that should escalate immediately
Escalate when the request involves identity mismatch, former staff access, unclear approver authority, or sensitive permission broadening.
Escalate when the request could expose financial, pastoral, or people-data visibility beyond what the church expected.
How to keep the request safe
Describe the access problem, the affected role, and the business consequence without sharing unnecessary sensitive detail in broad chat.
Use a narrower intake or review path when the case needs verification, not just explanation.
Escalation path
When identity, permissions, or approver authority is unclear, escalate into narrower handling instead of trying to resolve it through generic reassurance.