Appearance
Permissions and segregation of duties
Also known as
- roles
- permissions
- RBAC
- role-based access
- access control
- access rights
- user rights
- SoD
- segregation of duties
- separation of duties
What each person can see and do in Roari ERP comes from their roles. A role is a named set of permissions; a user holds one or more roles, and their access is the sum of those roles. Segregation-of-duties (SoD) rules stop one person from holding two permissions that together allow fraud or error, such as creating vendors and paying them.
How access works
| Piece | What it is | Example |
|---|---|---|
| Permission | One thing you may do, written module.resource.action. | finance.journal.post, sales.order.approve, inventory.receipt.create |
| Module permission | A whole module at once, written module.*. | finance.* gives every Finance permission, including ones added later. |
| Role | A named set of permissions. | Finance: finance.*, planning.*, analytics.*, reports.view … |
| User | Holds one or more roles. Permissions add up across roles. | Bruno Baker holds Employee self-service, Finance and Purchasing. |
| Account admin | The system role with full control of every enabled module. It cannot be edited or deleted. | Alex Admin |
| Portal role | A role for people outside the organisation, such as vendor contacts. | Vendor portal |
A permission works only while its module is enabled for your organisation.
What you see follows your permissions:
- Sidebar entries, settings pages, command palette actions and dashboard widgets you cannot use are hidden.
- Buttons for actions you may not take (Approve, Post, Delete …) are hidden or disabled, with the reason on hover.
- If you open a link to something you may not see, the page says you do not have access.
Differences by role
- Account admin sees and does everything in the enabled modules, including Settings.
- Vendor portal users (every role a portal role) see only the portal pages: no home dashboard,approvals, reports or other modules. See Vendor portal.
- Platform administrators of your provider can enter your organisation for support; everything they do is recorded in the audit trail as done on behalf of the platform.
The demo roles
| Role | Main permissions | Demo user |
|---|---|---|
| Account admin | Everything (system role) | admin |
| Finance | finance.*, planning.*, analytics.*, reports, dashboards, audit | finance |
| Purchasing | procurement.*, supply_chain.*, catalogue items | buyer |
| Sales | sales.* | sales |
| Warehouse | inventory.*, manufacturing.*, quality.*, catalogue items | warehouse |
| HR | hr.*, view users | hr |
| Projects | projects.* | pm |
| Service agent | service.*, assets.* | agent |
| Employee self-service | hr.self.service (own payslips, leave, timesheet) | most users |
| Vendor portal (portal role) | supply_chain.portal.vendor | vendor1 |
Create a role
- Open SettingsRoles and permissions and select New role.
- Type the Name (for example
Accounts payable clerk) and a Description. - Switch Portal role on only for a role meant for outside contacts.
- Under Permissions, tick what the role may do. The matrix has one row per resource and one column per action (View, Create, Approve, Post, Export …):
- type in Filter modules, resources or permissions to find a permission;
- tick a module's row to grant all its permissions, a resource's last box for Every action on it, or a column header for that action on every resource;
- use Grant all or Clear all for everything shown.
- Read the warning above the matrix, if any (see below).
- Select Create role.
The role shows in the list with its number of permissions. Change it later the same way and select Save role. Delete role is possible only once no user holds the role ("Remove this role from its users first.").
Give a user their roles
- Open SettingsUsers and select the user.
- In the Roles panel, add or remove roles in Roles.
- Select Save roles.
If the user is signed in, ask them to reload the page or sign in again to get the new access. A user keeps at least one role ("Keep at least one role."), and you cannot change your own roles ("You can't change your own roles; ask another administrator."). See User detail.
Segregation of duties
SoD rules live in the Compliance module, grouped in rule sets. Each rule names two permissions that should not be held by the same person, a risk level and an enforcement:
| Enforcement | What happens when a user would hold both permissions |
|---|---|
| Block | Assigning the roles is refused: "Segregation of duties: this combination of roles is blocked by ITG-01 Manage users and roles". The attempt is logged. |
| Warn | The assignment goes through; a violation is recorded and the SoD managers get a Segregation of duties notification. |
The demo organisation has these rules:
| Rule | Conflicting duties | Enforcement |
|---|---|---|
| ITG-01 | Manage users and roles (settings.users.manage with settings.roles.manage) | Block |
| ITG-02 | Create and post journals | Block |
| ITG-03 | Maintain employees and run payroll | Block |
| P2P-01 | Maintain vendors and pay them | Warn |
| P2P-02 | Create and approve purchase orders | Warn |
| P2P-03 | Approve orders and receive goods | Warn |
| P2P-04 | Enter vendor bills and approve payments | Warn |
| O2C-01 | Maintain customers and post receipts | Warn |
| O2C-02 | Create and approve sales orders | Warn |
| O2C-03 | Change prices and approve orders | Warn |
Check a role before you assign it
The role editor checks the permissions you tick against the enforced rules and shows a warning above the matrix, for example: "These permissions break a segregation-of-duties rule: assigning this role to a user will be refused." with each rule, its two permissions and "(blocked on assignment)" or "(warned on assignment)". Saving the role is still allowed: the check that counts happens when the role is given to a user.
Review conflicts across the organisation
- Open ComplianceSegregation of duties.
- On Violations, filter by Status, Risk, Subject or Rule set and open a violation to see the roles that cause it.
- Accept a conflict you cannot remove (a small team, for example) by recording a compensating control on Mitigating controls. A mitigated conflict no longer blocks.
- Use Analysis and simulation to test a role or user change before you make it, and Run analysis to recheck everyone.
See Segregation of duties, Sod rule sets and Sod analysis.
Approvals and four-eyes control
Permissions say who may act; approval rules say who must agree. Combine them for maker-checker control: the buyer creates the purchase order, a different person approves it in Approvals. Name approvers by role, user or the requester's manager so that the approver is never the person who raised the document.
Permissions to manage access
| What | Permission |
|---|---|
| See users / roles | Permission: settings.users.view / Permission: settings.roles.view |
| Manage users | Permission: settings.users.manage |
| Manage roles and permissions | Permission: settings.roles.manage |
| See and manage SoD rules and violations | Permission: compliance.sod.view / Permission: compliance.sod.manage |
Under rule ITG-01, the same person should not both manage users and manage roles. Give these to two administrators.
Limits and gotchas
- Permissions only add up: there is no "deny". To take something away, remove it from the role or remove the role.
module.*includes permissions a module adds in later versions. Tick individual permissions for a role that should stay narrow.- API keys carry their own permissions, chosen when the key is created in API keys.
- Removing a role does not change documents the user already created or approved; the audit trail keeps who did what.
