Least Privilege Without the Jargon: Who Should Be Able to Do What
Everyone being an admin is the default in small firms because it is easier. Here is how to cut back permissions without grinding the work to a halt.

A twelve-person consultancy sets up Microsoft 365. The person doing the setup makes themselves a global administrator, which is necessary. Then the office manager needs to add a new starter, so she gets global admin too. Then the external IT contractor needs access, so he gets one. Then someone is on holiday during a password reset emergency, so a fourth person gets it "temporarily". Three years later, eight of the twelve are global administrators and nobody remembers which grants were deliberate.
That is how privilege accumulates in small organizations. Not through carelessness, exactly, but through a long series of individually reasonable decisions that nobody ever revisits.
What least privilege means when you have twenty staff
Least privilege is the idea that an account should be able to do what its owner's job requires and nothing more. The important word is account, not person. You are not making a judgement about whether someone is trustworthy. You are deciding how far an attacker gets if that particular login is stolen, because a stolen account inherits every permission the real owner had. MITRE's attack library catalogues this as the use of valid accounts, and it is one of the most common ways intruders move around a network precisely because it generates no alarms.
In a large company this becomes an entire discipline with tooling and approval workflows. In a small one it reduces to a handful of specific decisions you can make in an afternoon.
Start where the consequences are largest
Do not try to audit every folder on your file share. Start with the permissions that would let someone rewrite your organization.
Administrator roles in your email and office suite
A global or super administrator can read any mailbox, reset any password, turn off security settings and add new accounts. Both Microsoft 365 and Google Workspace ship with narrower prebuilt roles that cover most of what people actually need: a user management admin who can create accounts and reset passwords but cannot change security policy, a help desk role, a billing role. Most of the people who currently hold full admin in a small business need one of those instead.
Keep at least two full administrators so a single absence cannot lock you out, and give those people separate accounts for admin work rather than doing it from the mailbox they read email in. That separation matters more than almost anything else on this list, and it is covered properly in administrator account security.
Finance, payroll and payment platforms
Ask a different question here: who can change where money goes. Not who can see invoices, but who can add a new supplier, edit bank details, approve a payment or alter payroll. In many small firms that list is longer than anyone expects, because the accounting package was set up with one access level and never revisited. Attackers who target payment processes are specifically looking for an account that can perform the change without a second pair of eyes.
Your domain name and DNS
Whoever can log into your domain registrar can redirect your website and your email. It is frequently the smallest access list in the business and the least thought about. Keep it to two named people and see domain name security for the locks worth turning on.
The three places privilege quietly expands
Shared logins. A shared account defeats least privilege by definition, because everyone who has it holds the maximum permission it carries. If four people use one supplier portal login, you have granted four people full access to that portal and you cannot take it back from one of them. See shared accounts for the alternatives.
Local administrator on laptops. If everyone's day-to-day Windows or Mac account is an administrator, then any malicious installer they run inherits that. Setting staff up as standard users, with an admin password held by whoever manages IT, means software installation becomes a short conversation. That is friction, and it is the useful kind.
Connected apps. Third-party tools that ask to connect to your email or file storage are requesting permissions on behalf of an account, and those permissions persist long after anyone stops using the tool. Consent requests are also an attack route in their own right. Check the connected app list in your office suite admin console once in a while and revoke what nobody recognizes.
Make it a role baseline, not a series of favours
The failure mode in small firms is handling every permission as an individual request, which means grants happen and removals do not. The fix is to write down, roughly, what each role gets. Not a formal document. A page.
- Everyone: email, calendar, the general file areas, the collaboration tool, two-step verification turned on.
- Finance: the accounting package, the banking portal, the payroll system. Nobody else.
- Managers: their team's folders, the HR system if they need it.
- Whoever manages IT: separate admin accounts for the office suite and the registrar.
Then new starters get their role's baseline and nothing else, which is the cheapest moment to get this right. See security onboarding. Anything outside the baseline is a request, and a request with an end date where the work has an end date. Contractors and temporary project access should always carry one.
Temporary access that actually ends
"I just need admin for this one task" is a reasonable thing to say and a terrible thing to grant permanently. The small-business version of time-limited privilege does not need special software. It needs a line in a shared note: who was granted what, by whom, and the date it comes off. Then someone takes it off on that date. Large platforms automate this with just-in-time elevation, and if your subscription tier includes it, use it. If it does not, a calendar reminder genuinely works.
There is one exception worth planning for deliberately: the emergency account that exists so you are not locked out of your own systems when the usual administrator is unreachable. That needs to exist, and it needs guardrails, which is a topic of its own in break-glass access.
What to do in the next hour
- Open your office suite admin console and list everyone with a full administrator role. Write down why each one has it.
- Move everyone who does not need full admin onto a narrower prebuilt role.
- List who can change supplier bank details or run payroll, and confirm each name is deliberate.
- Check who can sign in to your domain registrar.
- Put a date in the calendar three months out to do it again, properly, as an access review.
None of this costs money, which makes it unusual among security improvements. If budget is the constraint you are working under, it belongs near the top of the list in security on a small budget, alongside the access changes that come with every joiner and leaver in joiners, movers and leavers.
Got a message asking you to approve access or reset a password? Paste it into CyberWatch AI Scan for a free check before you click anything.
Cutting permissions back does not stop an attack starting. It decides how much of your business is reachable once one does, which is usually the difference between an incident and a disaster. For the wider picture, see protecting small businesses from digital threats.
Frequently asked questions
What does least privilege actually mean?
Each account can do the things that person's job requires and nothing more. It is a statement about accounts rather than about people, because an attacker who steals an account inherits exactly what that account can do.
How many administrators should a small business have?
At least two, so a single illness or departure cannot lock you out, and as few beyond that as you can manage. Two or three is normal for a team of twenty.
Is least privilege about not trusting staff?
No. Most privilege problems have nothing to do with intent. The risk is that a phished account, a lost laptop or a mistaken click reaches further than it needed to.
What if a tool only has one permission level?
Some small SaaS products only offer full access. Note it, limit who holds the login, put the credential in a business password manager, and treat that tool as a known gap you check at review time.
Should staff have administrator rights on their own laptops?
Usually not for routine work. Day-to-day accounts should be standard users, with an administrator password available for installing software, which is a sensible friction point rather than a blocker.
Does least privilege slow people down?
Done badly, yes. Done well it is invisible most days because the baseline for each role already contains what that role needs, and the rare exception is a short request with a quick answer.
How is this different from an access review?
Least privilege is how you decide what to grant. An access review is the periodic check that what you actually granted still matches that decision. You need both because permissions drift.
Where should a small business start?
With administrator roles in your email and office suite, then finance and payroll, then whoever can change your domain name settings. Those three carry far more consequence than file folders.
Sources
- Identity and access management, UK National Cyber Security Centre
- Small organisations guide to cyber security, UK National Cyber Security Centre
- Valid Accounts, Technique T1078, MITRE ATT&CK
- Account Manipulation, Technique T1098, MITRE ATT&CK
- Privileged roles and permissions in Microsoft Entra ID, Microsoft Learn
- Prebuilt administrator roles, Google Workspace Admin Help
- IR 7621 Rev. 1, Small Business Information Security: The Fundamentals, NIST
- Zero Trust Maturity Model, US Cybersecurity and Infrastructure Security Agency


