Role-based access: who should see what in your firm
How to design sensible roles and permissions so every team member sees exactly what they need, and nothing they don't.
As a practice grows, the question of who can see what becomes harder to answer informally. A sole practitioner can keep it all in their head; a firm of fifteen cannot. Role-based access control gives you a clear, repeatable way to decide permissions, and it reduces both accidental mistakes and deliberate misuse.
Why roles beat per-person settings
It is tempting to grant access one person at a time as requests come in. That approach quietly becomes unmanageable: permissions drift, nobody remembers why someone has access to a client, and offboarding gets messy. Roles solve this by grouping permissions around the job, not the individual.
- Consistency. Everyone in the same role gets the same access, so there are no surprises.
- Speed. Onboarding a new bookkeeper is a single role assignment, not a checklist of toggles.
- Auditability. You can answer "who can see payroll?" by looking at one role, not twenty profiles.
- Cleaner offboarding. When someone leaves, removing or reassigning a role is far simpler than unpicking a tangle of individual grants.
A starting set of roles
Most practices can begin with a small number of clear roles and refine over time.
Administrator
Manages users, billing and configuration. Keep this group small. Two administrators is usually enough for redundancy without spreading high privilege too widely.
Manager or partner
Sees their portfolio of clients, assigns work and reviews output. May have visibility across teams where oversight is needed.
Preparer or bookkeeper
Works on assigned clients and jobs. Does not need the whole client list or firm-wide financial settings.
External or client user
Through a client portal, a client sees only their own information, approvals and documents, and nothing belonging to anyone else.
Apply least privilege, then review
The guiding principle is least privilege: grant the minimum access needed to do the job, and widen it only when there is a real reason. This feels cautious, but it is far easier to add access than to discover, after an incident, that everyone could see everything.
Schedule a light review every few months. Look for people who changed roles but kept old access, dormant accounts, and clients shared more broadly than necessary. A common trap is the staff member who moves from a junior role into management and accumulates the access of both. Reviewing against roles, rather than against memory, catches that drift early. Tools that support per-workspace isolation and role-based access, including platforms like Finye, make these reviews quick because permissions are structured rather than ad hoc, so you can see at a glance who sits in each role.
Takeaway: define three or four clear roles, assign people to them rather than hand-tuning individuals, and put a recurring permission review in your calendar so access stays aligned with what people actually do.