Every privileged action and every denied attempt is written to a record that nobody can edit or delete.
When a gift is voided or a role is granted, someone will eventually ask who did it and why. Without a record the answer is a guess, and trust suffers.
Granting a role, voiding a gift, approving a ledger entry, accepting a monthly report, reviewing a membership, reading a care case, deleting a group or a record: each writes an entry beside the action.
When someone tries something they are not allowed to do, that is recorded as well, with the same detail.
Nobody approves a ledger entry they created or changed, or accepts a report they sent. Approved entries are locked: a correction is a new entry, and the old one stays visible as voided.
Narrow the list by who acted, what they did (for example everything that starts with donation.), the outcome and the time.
Entries are kept for the period the platform sets, 730 days by default, then removed automatically. Until then nobody can change them.
Audit trail
Sample dataReading the trail is its own permission, held by the built-in Auditor role. Give it to the people you choose. A separate Finance auditor role reads every unit’s books and reports without changing them.
The trail can say that a care case was read, but never shows the private notes in it.
Entries never hold passwords, tokens or the text of private notes.
Built-in roles for treasurer, records clerk, care minister and more, custom roles, and access granted to people or whole groups.
See how it works: Roles and accessChurches 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.