Built-in roles for treasurer, records clerk, care minister and more, custom roles, and access granted to people or whole groups.
Most churches run on volunteers. The treasurer should not read pastoral notes, and the clerk who keeps baptism records should not see the offering. One shared administrator password is the usual workaround, and it leaves no trail.
Treasurer, records clerk, care minister, event coordinator, attendance taker, auditor, IT administrator and more, each with a plain description of what it allows.
Choose exactly the permissions a role needs from the full list and give it your own name, such as Sunday school coordinator.
Grant a role to one person or to a whole group. Members of the group hold the role for as long as they belong to it.
Every active member can browse the members directory and the groups. Everything else has to be granted.
Roles and access
Sample dataChanging who holds a role is itself a permission, marked privileged, and every change is written to the audit trail.
A report only reads data its builder was already allowed to see.
Hiding a button is a convenience. Every request is checked against the person’s roles in your church before anything happens.
Every privileged action and every denied attempt is written to a record that nobody can edit or delete.
See how it works: Audit trailEvery church starts with All members only. Apply the EOTC church structure or a regional one from Admin → Starter templates, or build your own.
See how it works: Structure and templatesChurches kept apart, roles given per department, a second person for money and reports, privacy settings per member, consent on record, verified sign-in, rate limiting and session control.
See how it works: Security and privacyRegister your church and start with your profile, or write to us first with your questions.