Role-based access control
In Arabic التحكم في الوصول حسب الدور
Role-based access control (RBAC) is a way of managing system access in which permissions are granted to roles, and users gain access by being given a role.
In plain words
Granting rights user by user stops working as soon as the team grows. With RBAC you define once, as a role, what a sales clerk, a storekeeper or an accountant may do, and give each person the role that fits their job. A change to the role reaches everyone in it.
Each role holds a level per area of the system, such as view, create, edit or approve. Approval is often kept as its own level, so the person who enters a document is not automatically the one who can release it.
The common mistake is checking access only in the menu. A hidden button does not stop a request sent another way. The server has to check every change against the user’s role, whatever the screen shows.
- Role
- Sales clerk
- Level on sales orders
- Edit
- Action
- Release a credit hold
- Level needed
- Approve
- Outcome
- Refused
In Axon Suite
How Axon Suite handles it
In Axon Suite every user holds one role, and every role holds a level per area from View to Approve. Five starter roles come ready, and the server refuses a change the role does not allow.
Feature
Roles that decide who does what
Every user holds one role, and every role holds a level per area: View, Create, Edit, Full or Approve. Without the level, the screen turns read-only and the server refuses the change all the same.
Open: Roles that decide who does what