
A permissions matrix: who can access what, and who keeps it current
A permissions matrix records which job role may use which system and which folder, and at what level. On paper it is an afternoon’s work. The hard part comes afterwards: turning the matrix into groups in your environment, and making sure it still holds after someone has changed roles three times.
A permissions matrix describes rights per role, not per person. Anyone who needs an exception gets it as an exception, with a reason and an end date.
In the environment itself, rights are attached to groups and never to individual accounts. A role change is then one change instead of twenty.
The matrix only stays accurate with an owner per system and a fixed review. Who may access what is the organisation’s decision; we carry it out.
What a permissions matrix is, and what it is not
A permissions matrix is a table. The rows are the job roles in your organisation, the columns are systems and sets of data: the finance system, HR records, project folders, the CRM, the purchasing team’s shared mailbox. Each cell holds one level: no access, read, edit or manage.
The point is to have an answer to one question that does not depend on anyone’s memory: why does this person have access to this system? The answer should be “because they hold this role”, not “because it was set up that way once”.
What a permissions matrix is not: a list of admin rights. Who may configure servers, the tenant or the firewall is a separate subject with its own rules (separate admin accounts, rights only when needed) and belongs in its own register. This matrix is about ordinary work: who sees and edits which data.
Start with roles, not people
The temptation is to copy the current state: write down, per employee, what they have today. That produces a matrix that records every mistake you have now. Work the other way round:
- Get the list of roles from HR. Not the names, the roles. In most small and mid-sized organisations there are fewer than you think, and several turn out to do the same work.
- Define a baseline role everyone gets. Email, the intranet, the general folders, the ticketing system. Anything in that baseline no longer needs naming per role.
- Per role, fill in only what comes on top. That keeps the matrix readable and shows at once where a role carries a lot of special rights.
- Ask of every cell: does this role need it to do the job? “Convenient” and “the last person had it” are not reasons.
Only then do you put the current state next to it. The difference is your work list: rights that need removing, and sometimes rights that are missing and that people currently work around through a colleague.
How many access levels you need
Three or four levels is enough: read, edit and manage (may also change other people’s access), with “no access” as the empty cell. More levels look more precise, but nobody can later explain the difference between “edit” and “edit restricted”.
Two things deserve their own marking in the matrix:
- Segregation of duties. Combinations one person must not hold, such as creating a payment and approving it, or setting up a supplier and paying its invoices. Write them in as rules and a conflict shows up before it is configured.
- Exceptions. Someone covering for a colleague for a few weeks, or working on a project. They get the right as an exception, with the name of whoever approved it and an end date. An exception without an end date is, a year later, a permanent right nobody remembers.
From matrix to environment: groups, not people
A matrix on paper protects nothing. It only works when the environment follows it, and that only happens when rights are attached to groups and never to individual accounts. One group per role; that group gets access to the SharePoint site, the folder or the shared mailbox. An employee joins the group for their role and inherits everything that comes with it.
You see the benefit at every change. A new starter is one group membership. A role change is joining one group and leaving another. Anyone who asks during an audit who can reach the finance system gets a member list instead of a search through twenty settings.
In Microsoft 365 groups can also fill themselves from a field in the user profile, such as department or job title. That only works if HR keeps those fields reliable; otherwise you move the error from one place to another. Business applications such as the finance or ERP package often have roles of their own; they belong in the same matrix as a column, even when someone else configures them. How access, MFA and admin rights fit together is covered on our access management page.
Joiners, movers and leavers
The matrix is used at three moments, and each needs a fixed route: who requests, who approves, who carries it out.
- Joiners. The manager passes on the role, IT puts the new starter in the group for that role. No loose requests like “just give him what she has”.
- Movers. This is where it usually goes wrong. New rights are added quickly because someone asks for them; old ones are rarely removed because nobody asks. After a few moves, someone can reach everything. Make removing the old group part of the same change.
- Leavers. Account disabled, group memberships removed, any shared passwords they knew changed. On the last working day, not when somebody notices.
Let HR be the trigger rather than the employee. A role change is in the HR system before anyone thinks of raising a ticket.
Who keeps the permissions matrix current
Every column in the matrix gets an owner: the person in the organisation responsible for that data. The finance manager for the finance system, HR for personnel records. The owner decides who may have access; IT carries it out. That is not a formality: IT does not know whether a project manager should see salary data, and should not be the one deciding.
On top of that, a regular access review: at least once a year, more often for sensitive systems. The owner receives the member list of their groups and signs off that it is right. It takes about a quarter of an hour per system and it finds something every time.
If you work to ISO/IEC 27001, the standard expects access rights to be granted, reviewed and removed according to a defined process; a maintained matrix with its reviews is the evidence. UK GDPR asks for appropriate measures to secure personal data, and limiting who can reach it is the most obvious of them.
Where our work stops
What we do. We help set up the matrix from the list of roles, compare it with current access, build the groups in Microsoft 365 and on the file environment, and carry out changes through a fixed route. For each review we supply the member lists to the owners.
What we do not do. We do not decide who in your organisation may see which data; that is for the owner of that data and for management. Roles inside third-party business applications, such as an ERP or payroll package, are configured by the supplier or administrator of that package; we record them in the matrix. And we are not an auditor: whether your set-up meets ISO/IEC 27001 or data protection law is assessed by a certification body or your data protection officer.
Questions about permissions matrices
The five we hear most often.
What is a permissions matrix?
A table that records, per job role, which systems and data someone may access and at what level: no access, read, edit or manage. It makes access explainable: someone has access because they hold a particular role, not because it was once set up that way.
How do you create an access rights matrix?
Start from the list of roles held by HR, not from each employee’s current access. Define a baseline role everyone gets, add per role only what comes on top, then compare the result with the current state. The difference is the list of rights to remove or add.
What is the difference between a permissions matrix and role-based access control?
Role-based access control is the method: rights are attached to a role rather than a person. The permissions matrix is the document that sets out those roles and their rights. In the environment, each role becomes a group, and an employee inherits the rights by joining the group for their role.
How often should access rights be reviewed?
At least once a year, and more often for sensitive systems such as finance or HR records. Have the owner of each system check and sign off the member list of their groups. The matrix should also be updated at every role change, not only at the annual review.
Do you decide who gets which access?
No. Who may see which data is decided by the owner of that data within your organisation. We help set up the matrix, build the groups, carry out changes and supply the member lists for a review. Whether the set-up meets a standard is for an auditor to assess, not for us.
Further reading
What the permissions matrix connects to.
Shall we put your access next to your list of roles?
Send us your list of roles and the systems that matter. We will show which rights currently sit on individual accounts and what a matrix built on groups looks like; who may access what remains your decision.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.