Administration – User RBAC (Role-Based Access Control)
The User RBAC module allows system administrators to manage user roles and access areas within the Inventory Management System. This controls what permissions users have and which parts of the system they can interact with.
Each user can be assigned one of three roles: User, Approver, or Admin. These roles determine their access level and approval responsibilities.
Accessing the User RBAC Screen
From the top navigation:
Inventory Management > Administration > User RBAC
You’ll be taken to the User Role Assignment screen, where all existing user-role combinations are listed in a searchable and filterable grid.
Roles Overview
Role | Description |
---|---|
User | Can make inventory transactions. No approval permissions. |
Approver | Can make transactions. Will receive approval requests for any transaction exceeding $5,000. These requests appear in the My Approvals panel (left-side navigation). |
Admin | Full access to the system. Can make transactions, approve transactions, and manage users and settings. |
Main Grid Columns
Column | Description |
---|---|
User Email | The email address of the assigned user. |
Role | One of: Admin, Approver, or User. |
Area | The operational area the role applies to. "ALL" applies system-wide. |
Actions | Edit (✏️) or delete (?️) the user-role assignment. |
? A single email can be assigned multiple roles across different areas if needed.
Adding a New User Role
Click the + New button (top right).
Enter the following:
User Email
Role (User, Approver, Admin)
Area (e.g., AREA 1, AREA 2, or ALL)
Click Save.
The user will now appear in the list with their assigned role.
Editing or Removing a Role
To update a role, click the ✏️ icon beside the row, make your changes, and click Save.
To remove a role, click the ?️ icon. You’ll be prompted to confirm deletion.
Approval Workflow for Approvers
When an Approver is assigned:
They’ll automatically receive approval notifications for transactions over $5,000.
These notifications appear in the My Approvals section in the left navigation.
The approver can approve or reject the request before the transaction is finalized.
⚠️ If no approver exists for the area or transaction, it may be blocked or default to admin escalation depending on your company’s approval flow setup.
Best Practices
Assign at least one Approver per area to ensure large-value transactions are not delayed.
Use the "ALL" area for users who need global system access.
Avoid giving Admin access unless necessary—Admins have full control over the system.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article