1. Why permissions become a problem
In a partnership firm, permissions almost always accumulate in stages. A collaborator gets access to a case for an urgent assignment, then to a shared folder, then to the management system for a deadline. When the assignment ends, nobody goes back to remove the permissions. After a few years the firm discovers that different people can see case files they should not see, and nobody remembers who granted what.
The problem does not arise from bad faith but from the absence of structure. When permissions are assigned case by case, each decision seems reasonable, while the overall picture becomes impossible to control. Structuring access means moving from individual decisions to rules that apply to everyone, with clear owners. The result is a more readable system in which every access has a reason that can be explained.
2. What you need before you start
Before changing a single permission you need three things. The first is a list of the people working in the firm, with their actual role: owner, partner, internal collaborator, external collaborator, administrative staff. The second is a list of the systems and folders that hold confidential information, with an owner for each. The third is a decision on who can approve a new access and who can revoke it.
Without these three elements, any intervention will be partial. A permission removed from one folder can remain active on another application, and an approval given by someone who does not know the person's role produces the wrong access from the start. It is best to close this part before moving on to configuration. The time spent here is recovered during configuration, because decisions do not need to be revisited halfway through the work.
3. The steps to structure access
The order of the steps matters. The rules come before the tools, because a tool configured without rules reproduces the existing disorder with greater precision. Each step must close with a written decision, even a brief one, that the owner signs or confirms in writing. The written decision is what allows work to be resumed after an interruption without starting over. Keep the decisions in the same place as the access list, so that they stay connected.
The work can be done in a few meetings, with the IT supplier present for the technical part. It is useful to start from a real situation, with the current access list in front of you, rather than from an abstract model. The differences between what is written and what is configured are the work to be done. Assign each difference to an owner, with a date by which it must be closed.
- Map the actual roles: owners, partners, internal collaborators, external collaborators and administrative staff.
- Associate a standard set of permissions on systems and folders with each role.
- Create access groups corresponding to the roles and assign people to the groups, not individual permissions.
- Define exceptions, each with a justification, an owner and an expiry date.
- Establish the procedure for joining, changing assignment and leaving, with an expiry date for each temporary permission.
- Check with the supplier that the rules are actually applied, not just written down.
- Plan a periodic review and record its outcome.
4. Typical roles and what they see
Roles should reflect the work, not the formal organisation chart. Owners or partners normally have visibility of the whole firm, but even for them it is advisable to distinguish between managing the rules and accessing individual case files. A partner who administers the systems does not necessarily need to read every case, and keeping the two roles separate reduces the risk of errors and unintended misuse.
The internal collaborator sees the cases they handle and the common folders needed for day-to-day work. Administrative staff see what is needed for invoicing or secretarial work, without access to case file contents when it is not necessary. Each role should be described in a single line, so that whoever assigns it knows what is being granted. Briefly written roles are also easier to review when a collaborator changes assignment.
5. External collaborators and temporary access
External collaborators are the most sensitive point. They often work for several firms, use their own devices and remain active for long periods without anyone reviewing them. For them, access should be limited to the cases assigned, with an expiry date, and linked to a contract or written assignment that states the confidentiality required. The contract must also provide for the return or deletion of data at the end of the assignment.
Temporary access, for an intern or a stand-in, requires the same discipline. An account created for a short period must be remembered and closed at the end of that period, and the person responsible for the case must know when it expires. Automatic expiry, where the system allows it, avoids relying on memory. Where expiry is not automatic, it should be entered as a reminder that the responsible person receives in advance.
6. Common mistakes
The mistakes recur in very different firms and almost always have the same origin: a choice made in haste that nobody later reviewed. Knowing them helps you recognise them in your own firm before they become an incident involving a dispute to be handled. For this reason it is worth checking access before a problem emerges, not after. Even a few minutes' check, carried out regularly, prevents an error from staying hidden for months.
The most frequent is a permission granted to an entire group when it was needed for only one person, with the intention of correcting it later. Another is a shared account used by several people, which makes it impossible to know who did what. A third is a revocation carried out in the management system but not on the shared folder, because each system has its own list of access.
7. Periodic checks
Access should be checked at a fixed frequency, set by the owner and written into the procedure. The check is not a formal exercise: its purpose is to compare the list of active access with the list of people who actually work in the firm, and to close the differences. Anyone who has access they do not recognise must report it, and the report must be handled as an event to be recorded.
In the check it is also advisable to verify exceptions, which are the part most easily forgotten. Each exception must still have a valid justification and an expiry date. If it does not, it must be closed or renewed with a fresh approval, not left active out of inertia. Whoever approves the renewal should be the same person who defined the rule, so that the decision remains consistent.
8. How to get started
This week prepare a list of everyone working in the firm, with each person's actual role, and one of the most sensitive systems or folders with its current access. Comparing the two lists immediately shows the first anomalies, such as a departed collaborator who still has access or a permission granted to a group that is too broad.
Then arrange a meeting with the partners and the IT supplier to decide the first three standard roles and the rules for joining and leaving. The wider work can follow once the basic rules are written and applied at least once. The first application is the real test, because it shows where the written rules fail when faced with an actual deadline.
Frequently Asked Questions
Must a partner see all the firm's case files?
Not necessarily. A partner who manages the firm needs visibility suited to their role, which may differ from reading every case. Separating the management of rules from access to individual case files reduces risk. The choices should be decided by the partners themselves and written down, as they also concern each person's responsibility.
Can I use one account for all administrative staff?
This is not advisable. A shared account makes it impossible to know who did what and complicates revocation when someone leaves the firm. Each person should have a named account, even if the permissions are the same, so that the activity log remains readable.
How do I handle a collaborator leaving?
With a written procedure that lists all the systems the person had access to, including their work phone, email and shared folders. Revocation should be carried out on the same day as departure, on every system, and verified with the supplier. It is also advisable to recover work files and reassign open cases before the account is closed.
Who should approve a new access?
As a rule, the owner of the role or of the case, not the person who technically configures the system. Separating whoever approves from whoever configures reduces errors and leaves a trail of accountability. The rule should be written down and communicated to staff, with a single channel for requests.
Do I need a consultant to set up the structure?
Not always, but an external review helps when the firm has many exceptions or collaborators working for several organisations. The consultant can check the organisational and legal side, while the IT supplier covers the technical side. Ask both to work from the same map of roles.