Roles, access, and security
Sign-in, access, and security basics
User-facing security guidance should stay clear about access boundaries and avoid vague reassurance.
Who this is for: Admins and staff evaluating sign-in, permissions, and trust posture.
Last reviewed 2026-04-28 · Source of truth: launch shell · 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
- Use structured intake when the question touches identity or permissions changes.
- Keep security questions tied to explicit product behavior, not vague reassurance.
What the launch posture emphasizes
Transparent launch planning assumes explicit separation between church-user access and platform-admin powers.
Support or AI surfaces should never imply hidden privileges or backstage access they do not actually have.
When to escalate
Access edge cases, permissions uncertainty, and sensitive security questions should escalate instead of getting guessed answers.
Escalation path
Use structured intake when the issue touches permissions, identity, or sensitive access changes.