Key takeaways
- Write the access matrix as policy first — roles down the side, areas of the system across the top, and one of enter, edit, approve, view or none in each cell.
- Give each role the narrowest access its job needs; broad access "because it's easier" removes the control you were configuring.
- Match the matrix to your segregation rules: nobody should hold both custody and the record of the same asset.
- Software permissions are usually coarser than your policy — expect to enforce part of the matrix by routine rather than by setting.
- Individual logins matter as much as roles: shared accounts make every later review of "who did this" meaningless.
- Revisit access when someone changes job, and remove it the day they leave.
There are two ways to end up with access rights in a small business. One is to open the software's user settings and work out what looks reasonable per person. The other is to decide, on paper and away from the screen, what each job should be able to do — and then configure that.
The second produces a matrix you can defend, hand to a new hire, and check against later. The first produces whatever seemed convenient the week a new person started, which in practice means everyone has more access than their job needs.
This lesson is the policy exercise. The table below is an example to adapt, not a description of any particular product.
Write it as a grid
Roles down the side, areas of your system across the top. In each cell, one of: enter, edit, approve, view, or none.
| Role | Sales & invoicing | Purchasing | Cash & bank | Ledger & journals | Inventory | Reports | Users & settings |
|---|---|---|---|---|---|---|---|
| Owner | approve | approve | approve | view | view | view | edit |
| Bookkeeper | edit | edit | enter | edit | view | view | none |
| Sales | enter | none | none | none | view | own only | none |
| Purchasing | none | enter | none | none | view | own only | none |
| Warehouse | none | none | none | none | enter | none | none |
| Cashier | enter | none | enter (till only) | none | none | none | none |
| Outside adviser | view | view | view | view | view | view | none |
Read the grid against your segregation rules and check two things. First, no role holds both custody of an asset and the ability to adjust its record — the cashier enters till transactions but cannot post journals, and the warehouse records movements but does not adjust valuations. Second, no role can both create a payee and pay it, which is the phantom vendor route.
It is genuinely easier — on the first day. It also removes every distinction you spent the afternoon designing, and it is invisible afterwards, because nothing about a broad role looks wrong until something goes wrong.
Three principles that keep the matrix honest
Least privilege. Each role gets the narrowest access that lets the job be done. Access to information is a decision too: sales figures, margins and payroll do not need to be visible to everyone who enters transactions.
Individual logins. One account per person, always. A shared login means every subsequent question about who did something has no answer, which makes the monthly review an exercise in guessing. It also leaves honest staff unable to demonstrate that a mistake was not theirs.
Access follows the job, not the person. When someone changes role, their access changes with it — including losing what they no longer need. When they leave, access ends that day, not at the end of the month.
Where policy meets product
Most small-business accounting packages group permissions by module — sales, purchasing, accounting, settings — and offer something like full, read-only, or no access per module. Your matrix is finer than that: it distinguishes entering from approving inside the same module.
That gap is normal and manageable, as long as you are explicit about it. Go through the matrix and mark each cell as either enforced by the software or enforced by routine. A cell enforced by routine needs a named compensating control: a weekly report the owner reads, a second signature, a monthly review of that document type. What you must avoid is assuming a cell is enforced by the software because it seemed like it should be — which is exactly what the next lesson, verifying a feature before you rely on it, is about.
Reyuko implements access as seven preset roles — Owner, Accountant, Sales, Purchase, Warehouse, Cashier and Read-only. Each role carries its own matrix across the software's modules (sales, purchasing, inventory, accounting, contacts, products, settings, user management, deletion, reports, chart of accounts and point of sale), with each module set to full access, read-only, or none. The roles are fixed presets: they cannot be created, edited or deleted from the interface, so a role's scope cannot quietly widen over time.
Every user signs in with their own PIN, and switching between users requires that PIN — there is no silent user switch — so entries stay attributable to a person. Reyuko also auto-locks the session, which matters in a shared workspace where the screen is left open.
Two things to note when you map your matrix onto this. Access is set per module, not per action, so a role that can enter sales documents in a module can generally also edit them there — the enter-versus-approve distinction in your matrix is enforced by your routine, not by the setting. And because the seven roles are fixed, your matrix has to be expressed in terms of them rather than as custom roles.
Build and apply the matrix
- List your actual jobs, not idealised departments, and name a role for each.
- Fill the grid: enter, edit, approve, view or none for every role and area.
- Check it against your segregation rules — custody never sits with the record of the same asset.
- Mark each cell as enforced by the software or by routine, and name the routine where it is the latter.
- Give everyone their own login, and diarise an access review twice a year plus on every joiner, mover and leaver.
The matrix says what should be possible. The final lesson is about the difference between a rule your software enforces and a rule you are assuming it enforces — system-enforced controls.
Reyuko