Security

Protect church data while giving teams room to serve.

Church data can include members, children, prayer requests, pastoral notes, giving records, branch details, and private communication. The platform is structured around careful access and accountable workflows.

Secure technology workspace representing church data privacy

Security Principles

Role-based access

Admins, finance users, ministry users, community users, branch roles, and members see different parts of the system based on responsibility.

Sensitive record boundaries

Giving records, pastoral notes, prayer requests, exports, children-related details, and account settings should remain limited to authorized users.

Accountability

Individual accounts make it easier to understand who updated records, exported data, changed settings, or managed finance information.

Recommended Church Practices

Use individual accounts

Avoid shared passwords for staff, finance, media, and branch teams.

Review roles quarterly

Remove or reduce access when volunteers, staff, or branch assignments change.

Limit exports

Export only what is needed and store exported files carefully.

Write careful notes

Pastoral notes should be factual, respectful, and limited to what future care requires.

Data stewardship matters

The Rehoboth gives churches structure, but internal discipline still matters. Treat every profile, prayer request, and giving record as information entrusted to the church for service.