Your records, protected by design
Four application controls, explained in plain language — with diagrams, not walls of text. (The diagrams are explanatory illustrations, not product screens.)
Control 1 · Explanatory diagram — not a product screen
Access is deny-by-default
Nobody can do anything until the owner grants it. Grants are specific, revocable, and audited.
And deliberately: no super-administrator role exists inside the application.
Control 2 · Explanatory diagram — not a product screen
The audit trail only grows
Who did what, recorded permanently. Entries cannot be edited or deleted through normal application operations.
Accountant activity lands in the same trail, attributed to their own account.
Control 3 · Explanatory diagram — not a product screen
Finalized documents don't quietly change
Corrections happen in daylight: the original stays, and a visible linked document adjusts it.
Protected from silent modification through normal application operations.
Control 4 · Explanatory diagram — not a product screen
Period locks live in the engine
When an accounting period is locked, the lock is enforced in the accounting engine itself — not just hidden behind a greyed-out button.
The screen and the engine can never disagree about a closed month.
The unglamorous parts, done properly
Checked every request
Server-side sessions are checked on every request — revoking access takes effect on the next request.
Hashes, not passwords
Passwords are stored as strong one-way hashes, not plain text.
Attribution everywhere
Every member and every accountant acts under their own account — so the audit trail means something.
We describe application controls — how the product is designed and built. We don't decorate this page with badges or infrastructure promises we haven't earned yet; when there is something verified to say, it will be said here.
Ask us the hard questions
Governance is easier to show than to describe — request a demonstration and bring your accountant.