Who should see what: setting roles and permissions in a small company
How to apply least privilege in a small company: sort data into access levels, define roles, follow a step-by-step plan, handle joiners and leavers, and run a quarterly access review.

In a five-person company everyone can usually see everything, and that feels fine until it is not. A new hire sees salaries. A contractor opens client contracts. A departed employee still has access to the shared drive. None of that is malicious, but each one is a risk you can remove with a simple access plan.
This guide shows how to decide who should see and change what in a small company, using the principle of least privilege. It covers roles, a worked example, a leaver routine and a quarterly review. It draws on guidance from NIST, the US Small Business Administration, the FTC and CISA. General information, not legal or HR advice. Check employment and privacy rules for your state before you act on personnel records.
The principle: least privilege
NIST defines least privilege as giving each user only the access rights needed for their assigned work. The FTC puts it in plain terms: give each employee access only to the resources their job requires, and limit sensitive information to people who need it.
Why it matters even for small teams
- Fewer accidents. People cannot delete or change what they cannot edit.
- Smaller damage from a stolen login. If a phished account only reaches sales records, the attacker does not reach payroll.
- Privacy. Staff pay, health notes and client contracts are sensitive by nature.
- Trust and accountability. When access is clear, you can see who did what.
Map your data into access levels
Start by sorting information into a few levels. Three or four is plenty.
A simple classification
| Level | Examples | Who typically needs it | |---|---|---| | Public | Marketing pages, price lists | Everyone | | Team | Project plans, task lists, shared calendar | The people on that project or team | | Restricted | Client contracts, invoices, customer lists | Role holders such as sales, finance, account managers | | Confidential | Payroll, HR files, bank logins, admin settings | Owner, finance lead, HR lead |
Then map roles to levels
Think in roles, not people, because people change and roles do not. Typical small-business roles:
- Owner or admin: full access, plus the ability to change settings and roles.
- Manager: sees and edits their team's work and reports, approves requests.
- Team member: sees and edits their own projects and tasks.
- Finance: sees invoices, expenses and budgets, but not HR files.
- HR: sees hiring and employee records, but not client financials.
- Viewer or guest: read-only access to a specific project or folder, such as a contractor or client.
Build the access plan step by step
- List your systems: email, drives, accounting, CRM, chat, project tools, payroll.
- List your roles using the set above, adjusted for your business.
- For each role, write down what it can view, edit, delete and approve. Start with the minimum and add access only when someone asks and has a reason.
- Give each person one role, and a separate named account. No shared logins.
- Limit the admin group. The SBA advises limiting administrative access to trusted staff. CISA adds that people should not use administrator accounts for everyday work.
- Write it down on one page and store it where managers can find it.
A worked example
A ten-person agency has an owner, an office manager who also handles finance, two account managers, five designers and a part-time bookkeeper.
- The owner and office manager are admins, but the office manager uses a normal account for daily work.
- Account managers can see and edit client records and projects but not payroll.
- Designers can see and edit only the projects they are assigned to, and see tasks for their team.
- The bookkeeper gets finance access only, reaching invoices and expenses but not client files.
- Freelancers get guest access to one project folder and lose it when the project ends.
Joiners, movers and leavers
Most access problems appear when people change jobs, not at setup. The FTC advises collecting keys and ID badges and shutting off passwords when employees leave or change roles. The SBA similarly advises auditing access so that former employees are removed and company devices come back.
Checklists
- Joiner: create a named account, assign the role, enroll in MFA, share only the folders they need.
- Mover: remove old role access first, then add the new role. Do not stack permissions.
- Leaver: disable all accounts the same day, reset any shared passwords they knew, collect devices, forward their email to a manager, and review what they could access.
For the login side of this routine, see our guide to multi-factor authentication and passwords for teams.
Review access every quarter
CISA recommends auditing accounts quarterly to find and remove inactive or unauthorized ones, including third-party access. The FTC also points out that vendors, contractors and call center staff may have access too, so review theirs as well.
A 30-minute quarterly review
- Export or list every user in your main tools.
- Mark anyone who has left or changed roles.
- Check who has admin rights and whether each still needs them.
- Review guest and contractor access, and end anything that is not active.
- Check that sensitive folders and finance and HR areas are limited to the right roles.
- Note changes and keep the record with your other compliance notes.
Common mistakes
- Everyone is an admin "to avoid interruptions".
- Sharing one login between several staff or a bookkeeper and a manager.
- Permissions that only grow. People pile up access and never lose any.
- Forgetting contractors and vendors.
- No leaver routine, so accounts stay open for months.
- Setting access by person, not by role, which is hard to audit and easy to get wrong.
- Deciding once and never reviewing.
Where WorkBOS fits
Role-based access is built into WorkBOS: you assign people roles and set what each role can see and change across the product, an audit log records who did what, and the branded client portal gives clients their own limited view instead of a login to your internal tools. AI agents in WorkBOS act only with human approval, so a person stays accountable for what they do. The docs explain how roles work, the Academy has short setup lessons, and pricing shows plan limits, including the Free plan for up to 5 users. If you are consolidating tools, see run your business from one platform and our wider cybersecurity basics.
Frequently asked questions
Q: What is least privilege in simple words? A: Each person gets only the access needed for their job and nothing more. It limits mistakes and the damage from a stolen login.
Q: Should small teams really bother with roles? A: Yes. Even with five people, payroll, client contracts and admin settings do not need to be visible to everyone, and clear roles make adding staff easier.
Q: How many admins should we have? A: As few as you can manage, usually the owner and one trusted backup. The SBA advises limiting administrative access to trusted staff.
Q: What do we do when someone leaves? A: Disable their accounts the same day, reset any shared passwords they knew, collect devices and review what they could reach. The FTC advises shutting off access when employees leave or change roles.
Q: How do we give a contractor access safely? A: Use a guest or read-only role limited to the specific project, set an end date, and remove it when the work finishes.
Sources are linked in the text above: NIST, SBA, FTC, CISA.
Run it all from one place
Projects, clients, finance, people and AI employees in one system. Start free, no card needed.
Start free →