Standardized terminology for church roles, sacramental procedures, offline synchronization mechanics, and security boundaries.
A unique 8-character alphanumeric string (e.g., STMARY01) generated upon parish creation. Parishioners and servants enter this code during onboarding to link their user account to their specific church organization.
The ordained priest assigned to provide spiritual direction and confession to a parishioner. Koinonia OS maintains private, encrypted links between parishioners and their designated confession father.
The complete digital record of a church member, combining family household relationships, sacramental milestones, ministry participation, attendance logs, and financial giving histories.
The canonical records of ecclesiastical mysteries (Baptism, Chrismation, Matrimony, and Ordination). Koinonia OS generates authenticated PDF certificates bearing parish seals.
The progressive web app mechanism used by check-in kiosks to buffer attendance records in local IndexedDB storage during internet outages and automatically flush records to Supabase upon reconnection.
A dual-token security protocol during child check-in that generates identical alphanumeric codes or QR tags for children and their authorized guardian, preventing unauthorized departures.
The multi-tenant administrative tier managed by the Bishopric or Diocese office to monitor parish health metrics, approve cross-church servant transfers, and oversee diocesan events.
PostgreSQL database security policies implemented in Supabase that strictly isolate each parish's members, financial records, and confession logs by tenant_id.