Why Small Businesses Need Real Permission Systems Too
Permission systems have an enterprise reputation: committees, tickets, bureaucracy. But watch a six-person store for a week and you will see the actual need — a refund that should have been questioned, a margin visible to someone job-hunting at a competitor, an 'edit' to a filed month.
Two states aren't enough
Traditional software offers can and cannot. Real businesses run on a third state: allowed with supervision. The clerk SHOULD process returns — with a supervisor's nod. Hiding the button breaks the workflow; freely granting it breaks the control. The middle state — visible but requiring approval — is where most of a small business actually operates.
Approval by the right person, not the top person
'Find an admin' is how permission systems die in practice. The workable version lets ANY user who holds the right approve — the AR supervisor approves refunds, the accountant approves reopening a period — with their own password, for that single action, recorded. Authority distributes; accountability concentrates.
And it must be enforced below the UI
A permission that only hides buttons is theatre — anything that can reach the API can reach around it. In SeroBooks the same permission tree is checked by the server on the ledger, banking and marketplace endpoints. The app hides what you cannot see; the server refuses what you cannot do.
See it in your own numbers.
Free to start, on Windows, Mac, iPad and Android. No credit card.