Business

Role-Based Access Control: How to Design Permissions for a Business Application

November 11, 2026 · 4 min read · Etzal Group Team

Sooner or later every business application faces the same questions. Who may see salary data? Who can approve a payment? What can a branch manager see of another branch? Answering them one user at a time produces a system nobody can explain. Role-based access control, usually shortened to RBAC, answers them once, by job.

The model

RBAC has three layers:

  • Permissions are single actions on a type of record: view invoices, create purchase orders, approve leave, export customer data.
  • Roles are named groups of permissions that match a job: sales staff, warehouse supervisor, finance manager.
  • Users are assigned one or more roles.

When someone changes job, you change their role. When a job's responsibilities change, you change the role once and everyone holding it follows.

Step 1: list what can be done

Go through the application module by module and write down the actions that matter. Group them by record type:

  • Customers: view, create, edit, delete, export.
  • Invoices: view, create, edit, approve, cancel, export.
  • Payroll: view own, view all, run, approve.
  • Settings: manage users, manage price lists, view audit log.

Separate viewing from changing, and treat export and delete as their own permissions. Export moves data out of your control, and delete removes evidence.

Step 2: define roles from real jobs

Start from the organisation chart and from what people actually do, not from individuals. Write a one-line purpose for each role:

  • Sales staff: manages own customers and quotations.
  • Sales manager: sees the whole team's pipeline and approves discounts.
  • Finance staff: creates invoices and records payments.
  • Finance manager: approves payments and closes periods.
  • Administrator: manages users and settings, with no access to business approvals.

Then fill in a matrix with roles as columns and permissions as rows. A matrix on one page is the single most useful document in access design. Anyone can read it, and an auditor will ask for it.

Step 3: apply least privilege

Give each role only what the job needs. When in doubt, leave it out and add it when someone asks with a reason. Access that is granted "just in case" is rarely removed.

Pay particular attention to the administrator role. Technical administration, such as creating users, should not automatically include business powers, such as approving payments or viewing payroll.

Step 4: separate duties

For any process that moves money or changes critical data, no single role should control the whole path:

  • The person who creates a supplier should not approve payments to it.
  • The person who enters a payment should not be the one who releases it.
  • The person who runs payroll should not be the only one who approves it.

Enforce this in the system. A rule that says "the approver must differ from the creator" is one line of logic and removes a whole class of risk.

Step 5: add scope

Roles answer "what can this person do". Scope answers "to which records". Common scopes:

  • Own: records the user created or is assigned to.
  • Team or branch: records belonging to their unit.
  • All: everything in the company.

A branch manager and a regional manager may hold the same role with a different scope. Keeping scope separate from role avoids inventing a new role for every branch.

In systems that serve several companies, the tenant boundary is the outermost scope and must be checked on every request, on the server.

Step 6: enforce on the server

Hiding a button is not access control. Every request that reads or changes data must be checked on the server against the user's role and scope. Test this directly: sign in as a low-privilege user and call the address of a restricted action. It should be refused.

Step 7: log and review

  • Record who did what and when for sensitive actions, and record changes to roles themselves.
  • Review user access on a schedule, for example every quarter. Managers confirm that each person's access still fits their job.
  • Remove access on the day someone leaves or changes role. Link this to the HR process.
  • Handle temporary access with an expiry date.

Common mistakes

  • A role per person. The matrix becomes unreadable.
  • One all-powerful administrator account shared by several people. There is no accountability.
  • Permissions checked only in the interface.
  • No separation between viewing and exporting.
  • Access that only grows. Without reviews, people accumulate rights from every job they have held.

When RBAC is not enough

Some rules depend on the record itself: a manager may approve expenses up to a limit, or only for their own cost centre. These are handled by adding conditions to permissions. Start with simple roles and scopes, and add conditions only where a real rule requires them.

Access design, the permission matrix and server-side enforcement are standard parts of our Enterprise Software projects. If your current system has grown a tangle of individual permissions, contact us about a review.

Summary

List the actions, define roles from jobs, grant the minimum, split duties on anything involving money, add scope by branch or team, enforce every check on the server, and review access on a schedule. A one-page matrix that people can read is the sign of a design that will last.

Frequently asked questions

How many roles should a business application have?

As few as cover the real differences in what people do. Five to ten roles suit most mid-sized applications. When every person ends up with a unique role, the roles have stopped describing jobs and the design should be reviewed.

What is the difference between a role and a permission?

A permission is one allowed action, such as approving an invoice. A role is a named set of permissions that matches a job, such as finance manager. Users are given roles, and roles carry permissions. Assigning permissions directly to individuals becomes unmanageable quickly.

Why should the person who creates a payment not approve it?

Because one person controlling both steps can make an error or commit fraud without anyone noticing. Splitting the steps between two people is called separation of duties, and auditors look for it in any process that moves money or changes master data.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Free consultation

Not sure where to start? We will map the right system for your business, free.