Church Settings
Configure your selected church and manage approved church workspaces. Records always belong to the active church.
Active church
Church profile
Platform administration access
Checking your administrator access…
Create a church
Restricted to platform administrators. A new church is created with your administrator membership. The ID cannot be changed.
Access & users
Members of other churches cannot see your church's records. Church Administrators can review access requests for their own church.
Manage access requestsBackup & recovery
Verifying Church Administrator access…
Create a private archive of this church’s ministry records and Sunday attendance. No paid backup service is required. Files are not encrypted by Church OS; store them securely.
Maximum 10,000 records and 20 MB per file. Select a smaller attendance range for a large archive. Reads count toward the existing Firestore quota.
Backups include confirmed Firestore records only.
Open Attendance to sync pending changes
Recover missing records
Attendance recovery: Check-ins previously undone by staff may return because attendance undo has no retained deletion history. Restored entries keep the original Sunday and service; the recovering administrator and recovery time are recorded. Original audit values remain in the archive.
This manual archive is collected during a read window, not a point-in-time disaster recovery snapshot. User logins, access roles, platform settings, Ledger, device PINs, offline caches and unsynced attendance are excluded. Recovery never deletes records that are absent from a backup.
App lock
Protect this device's Church OS interface with a six-digit passcode. This is an additional privacy screen, not a replacement for Firebase sign-in. The PIN is stored as a salted derived hash on this device only.
Fingerprint: Not available yet. Device biometrics require a separately verified passkey integration. Church OS will not capture or store fingerprint data.