RBAC matrix templates.

Filled-in role and permission matrices for a SaaS product, an online store, a finance team and an agency, plus a blank one. Download any as a spreadsheet, or edit it in the builder.

By the NestedBit team · Updated

Pick a template

An RBAC matrix, or permission matrix, is a table with one row for each action on each resource and one column for each role. A mark shows where the role may act. Each example below is filled in, and each downloads as a spreadsheet you can edit in Excel or Google Sheets.

TemplateFitsRolesSpreadsheet
SaaS product A product sold to companies, where each customer has its own members, plus an AI assistant. 6 CSV
E-commerce store An online store with staff, a warehouse and customers who sign in. 5 CSV
Finance Expenses and invoices that someone must approve before anyone pays them. 5 CSV
Agency A team that delivers work to clients, who log in to see and approve it. 4 CSV
Blank Two roles and one resource, to fill in yourself. 2 CSV

How to read them

  • Yes means the role may take the action on any record.
  • Own means only on records that belong to the user. The spreadsheets write this as “Own only”.
  • An empty cell means no access. Anything not granted is refused.

Inherited permissions are written out in full, so you can read a role’s column without tracing other roles. In the builder, inherited cells show an arrow.

SaaS RBAC matrix example

Six roles for a product sold to companies. It’s multi-tenant, so a user’s role only counts inside their own customer organization.

Which roles may take each action in the SaaS product template
Resource Action OwnerAdminMemberViewerBillingAI assistant
Project read Yes Yes Yes Yes No Yes
create Yes Yes Yes No No No
update Yes Yes No No No No
delete Yes Yes No No No No
Document read Yes Yes Yes Yes No Yes
create Yes Yes Yes No No Yes
update Yes Yes Own No No Own
delete Yes Yes Own No No No
share Yes Yes Own No No No
Member read Yes Yes No No Yes No
invite Yes Yes No No No No
remove Yes Yes No No No No
change role Yes Yes No No No No
Billing read Yes No No No Yes No
update Yes No No No Yes No

Every permission applies within the user’s own customer organization. Owner inherits Admin. Admin inherits Member. Member inherits Viewer.

What the builder’s checks say about it:

  • Owner can do everything. Keep the number of people with this role small, and log what they do.

The choices worth checking against your product:

  • Billing is its own role. It manages billing and sees the member list, but no projects or documents, so whoever pays the invoices doesn’t need access to your customer’s work.
  • Admins can’t see billing. They run members and content, while billing stays with Owners and the Billing role.
  • Members edit only their own documents. They read all projects and documents and can create both, but only Admins and Owners update or delete projects.
  • The AI assistant inherits nothing. It reads projects and documents, creates documents and updates its own. It can’t delete, share or see members. Remove the column if you don’t have one.

E-commerce RBAC matrix example

Five roles for one store: four kinds of staff, and customers who sign in.

Which roles may take each action in the E-commerce store template
Resource Action AdminStore managerSupport agentWarehouseCustomer
Product read Yes Yes Yes Yes Yes
create Yes Yes No No No
update Yes Yes No No No
delete Yes Yes No No No
Order read Yes Yes Yes Yes Own
create No No No No Own
update Yes Yes Yes Yes No
cancel Yes Yes Yes No Own
refund Yes Yes No No No
Customer read Yes Yes Yes No Own
update Yes Yes Yes No Own
delete Yes No No No No
Discount read Yes Yes No No No
create Yes Yes No No No
update Yes Yes No No No
delete Yes Yes No No No

Admin inherits Store manager. Store manager inherits Support agent.

What the builder’s checks say about it:

  • Roles that differ by one permission. Admin and Store manager. Roles this close often mean a condition, such as ownership or an amount limit, is being modelled as a separate role.

The choices worth checking against your store:

  • Support can cancel but not refund. Refunds move money, so they stay with Store managers. Change this if your support team handles refunds, and add a limit in code.
  • The warehouse has no access to customer records. It can read and update orders, so keep what an order shows it to what shipping needs.
  • Only Admins delete customers. Customers can’t delete their own accounts here, so an Admin has to handle any deletion request. Add that action for customers if you’d rather they did it themselves.
  • Only customers create orders. If staff take orders by phone, give Support agents that action.

Finance RBAC matrix example

Five roles for expenses and invoices, built to keep requesting, approving and paying apart. This is the template where a matrix alone isn’t enough, as its warnings show.

Which roles may take each action in the Expenses and approvals template
Resource Action AdminFinanceManagerEmployeeAuditor
Expense read Yes Yes Yes Own Yes
create Own No Own Own No
update Own No Own Own No
submit Own No Own Own No
approve Yes No Yes No No
pay Yes Yes No No No
Invoice read Yes Yes No No Yes
create Yes Yes No No No
update Yes Yes No No No
approve Yes No No No No
pay Yes Yes No No No
Report read Yes Yes Yes No Yes
export Yes Yes No No Yes

Admin inherits Finance and Manager. Manager inherits Employee.

What the builder’s checks say about it:

  • Admin can create and approve Expense. Admin can create and approve Invoice. Manager can create and approve Expense. One person could approve their own request. Stop approvers approving their own records in code, or split the duties across roles.

The choices worth checking against your process:

  • Those warnings are real, and a matrix can’t fix them. Managers file their own expenses and approve others’, so your code must refuse approval when the approver submitted the expense. RBAC vs ABAC shows that rule in OPA Rego.
  • Finance pays but doesn’t approve expenses. That split only holds if your code also refuses to pay anything not yet approved. The same goes for invoices, which Finance can create and pay. A role can’t see a record’s status.
  • Managers can read every expense. To limit them to their own team, add a condition on department. That’s also beyond a role.
  • Auditors only read and export. They inherit nothing, so a new permission never reaches them by accident.
  • Admin inherits both Finance and Manager, which joins the duties this template keeps apart. Give that role to very few people, and log what they do.

Agency RBAC matrix example

Four roles for a team doing client work, with clients logging in to see and approve it.

Which roles may take each action in the Agency template
Resource Action OwnerAccount managerContributorClient
Client read Yes Yes No No
create Yes Yes No No
update Yes Yes No No
Project read Yes Yes Yes Own
create Yes Yes No No
update Yes Yes No No
delete Yes No No No
Asset read Yes Yes Yes Own
upload Yes Yes Yes No
update Yes Yes Own No
approve Yes Yes No Own
delete Yes Yes No No
Invoice read Yes Yes No Own
create Yes Yes No No
send Yes Yes No No

Owner inherits Account manager. Account manager inherits Contributor.

What the builder’s checks say about it:

  • Roles that differ by one permission. Owner and Account manager. Roles this close often mean a condition, such as ownership or an amount limit, is being modelled as a separate role.
  • Owner can do everything. Keep the number of people with this role small, and log what they do.

The choices worth checking against your agency:

  • For a Client, “Own” means their company’s records, not ones they personally created. Your code needs to link each project, asset and invoice to a client, and check that link.
  • Clients approve but never upload. They can approve their own assets, and see their own projects and invoices. Add upload if clients send you material through the same system.
  • Contributors can’t see client records or invoices. They read projects and assets, upload, and edit their own assets.
  • Contributors see every project. With a matrix alone, freelancers on one account can read all the others. To limit them, assign people to projects in your data and check that assignment in code.

Blank RBAC matrix template

Two roles and one resource, with the column layout and “Own” cells in place, ready for your own rows.

Which roles may take each action in the My app template
Resource Action AdminMember
Item read Yes Yes
create Yes Yes
update Yes Own
delete Yes Own

Admin inherits Member.

What the builder’s checks say about it:

  • Admin can do everything. Keep the number of people with this role small, and log what they do.

How to adapt a template

  1. Rename the resources to the words your product uses, then delete what you don’t have.
  2. Add the actions that carry risk, such as approve, refund or export. Keep them separate from update, so you can give them out one at a time.
  3. Cut roles until each matches a real job. Two roles with almost the same column are usually one role and a condition.
  4. Read one column at a time with someone who does that job. They’ll spot what’s missing, and what they’d never need.
  5. Run the checks in the builder for duplicate roles, unused roles and anyone who can approve their own work.
  6. Export it as code if you’ll enforce it that way: Casbin, OPA Rego, Cedar or Postgres row-level security.

What a matrix can’t show

A matrix answers “may this role take this action?” It can’t answer “on which records?” beyond ownership, or “under what conditions?” Team boundaries, amount limits, record status and approving your own request all live in code or in attribute rules. Those limits are listed under each template above.

If you keep adding roles such as “Manager, EU” or “Approver under $5,000”, that’s the sign to stop. Keep the roles coarse and add rules on top, as RBAC vs ABAC explains.

Free tool · No sign-up

RBAC Matrix Builder

Lay out roles, resources and actions in a grid, then export the matrix or working policy code.

Starts with a free 30-minute intro call, or email hello@nestedbit.com.