Access that grew without a plan
In a small business, access tends to accumulate. Someone is given the till login, then the payment app, then the shared spreadsheet, then the bank view. Years later, people who left still have access, new hires have more than they need and nobody can say who can see what.
An access map restores order. It is a plain table, not a technical project.
Make the map
List the systems that hold sensitive information or can move money: bank accounts, payment apps, point-of-sale, accounting tools, payroll files, customer lists, supplier records, shared drives, email accounts. Beside each, list who has access and at what level.
| System | Who | Level | Why |
|---|---|---|---|
| Bank account | Owner, accountant | View and approve | Control and filing |
| Payment app | Owner, manager | Collect and refund | Daily operations |
| Till or sales app | Counter staff | Sell only | Serve customers |
| Payroll file | Owner only | Full | Privacy of pay |
| Customer list | Manager | View | Deliveries and follow-up |
The table above is illustrative; build yours from your own business.
Apply least privilege
For each person, give the lowest level that lets them do their job. A counter employee does not need refund rights without approval. A delivery person does not need the full customer database. A bookkeeper does not need to move money. If someone needs more for a time, grant it temporarily and remove it afterwards.
Individual accounts
Avoid shared logins. Give each person their own access so you can see who did what and remove one person without disturbing others. Turn on the second step where available. Keep a list of devices permitted to use business accounts.
Joiners, movers, leavers
Handle changes at three moments. When someone joins, grant what their role requires. When they change role, adjust access and remove what is no longer needed. When they leave, remove everything on the same day, including shared passwords they may know. Keep a checklist and tick it off.
Customer and staff data
Where systems hold personal details of customers or employees, limit access further and keep a note of who has seen what. Educate staff on what not to share, such as photographing screens or forwarding lists. Remind them that these details belong to other people.
Reviews
Review the map every six months and after any incident. Check that former staff have no access. Check that the permissions still match roles. Ask each person whether they have access they do not use. People often point out forgotten permissions when asked.
Records of changes
Keep a log of access changes: who, what, when and who approved. It supports investigations and shows that you manage access carefully. A log is also a good thing to have if a customer or authority asks how you protect their data.
Start small
If this feels large, begin with the bank and the payment app, which carry the most risk. Fix those, then move on. An access map done in stages is worth far more than a perfect one that never starts.
A worked example
A shop owner draws up the map and notices that a former helper still has the payment app login, and that the sales spreadsheet is shared with a link that anyone can open. Within an hour she removes the former helper, creates individual logins and switches the spreadsheet to named people. Nothing had gone wrong yet, and now it is much less likely to. The map made visible what had quietly accumulated over the years.
Training and expectations
Give each person a few lines on what they may see and do and why. Explain that the limits protect them too: if something goes wrong in an area they cannot access, they are clearly not responsible. Staff generally accept boundaries that are explained fairly, and they become more careful with the access they do hold.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

