General

Role-based access control (RBAC): what it is and how it works

Role-based access control is a method of managing system access by assigning permissions to roles, then assigning people to those roles instead of setting permissions for each user.

Zigaflow Editorial

Published

Zigaflow Editorial publishes Zigaflow's guides, insights, industry resources, glossary and workflow pages. Zigaflow is responsible for what they say. Spotted an error? Email support@zigaflow.com.

In short

Role-based access control gives people permissions through the role they hold, not through individual settings. Define a few roles once, covering costs, exports and approvals, then assign each person to one.

Role-based access control (RBAC) is a way of managing who can see and do what in a system by attaching permissions to roles, such as sales rep, buyer or finance, and then assigning people to those roles. Without it, an administrator grants each user their own custom set of permissions, one setting at a time. With RBAC, the decision is made once for the role, and everyone in that role inherits it. When someone joins, changes job or leaves, you change their role rather than rebuilding their access from scratch.

How role-based access control works

An RBAC setup has three parts: users, roles and permissions. Permissions are specific actions, such as viewing cost prices, exporting a customer list or approving a purchase order. A role is a named bundle of those permissions. Each user is assigned one or more roles and receives only what those roles contain.

Roles are usually built around the job, not the person. A sales role might create and send quotes but not see supplier cost prices. A buyer role might raise purchase orders up to a set value. A finance role might see margins, approve invoices and export ledger data. IBM describes this as mapping permissions to roles, then assigning users to roles instead of granting access directly.

> Tip: Start with three or four roles that match how your business already works, then add more only when a real job cannot fit an existing one.

Why it matters for a small business

In a team of five, giving each person individual permissions feels manageable. By fifteen, it is not. Each person ends up with a slightly different combination, nobody remembers why, and access builds up as people take on extra tasks. The IBM implementation guide calls this privilege creep: users accumulate permissions from old roles and one-off exceptions.

RBAC lets an owner decide a few questions once:

  • Who can see costs and margins?
  • Who can export customer and pricing data?
  • Who can approve quotes, purchase orders or spend above a limit?

It also supports least privilege, the principle that people get the minimum access their job needs. And it supports separation of duties, where one person raises a payment or purchase and a different person approves it. IBM's guide gives the example that nobody should be able to both create a supplier and approve payments to that supplier.

Roles, groups and individual exceptions

RBAC is often confused with similar ideas. A job title is not automatically a role, although the two often match. A group is a collection of people, while a role is a collection of permissions. Some systems also allow hierarchical roles, where a manager role includes everything a team member role can do, plus more.

Exceptions will always arise. The risk is not the exception itself but forgetting it. Review roles periodically, and treat anything outside the standard roles as something to justify and revisit.

RBAC in business management software

In business management software, RBAC controls the commercial information that matters most: pricing, margins, customer records, approvals and data exports. Zigaflow's permissions and security features apply this approach so that access follows the role a person holds in the business, rather than a list of individual settings.

Frequently asked questions

Ready to put this into practice?

Book a demo and see how Zigaflow fits your team.