Roles & Permissions
Agora uses a high-precision, role-based access control (RBAC) system. This ensures that every staff member sees only the data they need to see and can only perform actions authorized for their specific job function.
Granular Permission Matrix
Permissions are managed via a matrix that defines access for every module in the application.
Action-Level Control:
For every module (Sales, Inventory, Expenses, etc.), you can define:
- View: Can the user see the records?
- Create: Can the user add new data?
- Edit: Can the user modify existing records?
- Delete: Can the user remove data?
- Export: Can the user print or download reports?
Dynamic Interface Adjustment
The Agora interface is "permission-aware." If a user does not have permission to view a module (e.g., Payroll), the corresponding menu item will be completely hidden from their sidebar, reducing clutter and preventing unauthorized access attempts.
Real-World Use Cases
- The "Junior Cashier" Role: A role configured to only allow "View" and "Create" permissions for Sales, with "Delete" and "Edit" disabled to prevent unauthorized transaction modifications.
- The "External Accountant" Role: A role with "View" and "Export" permissions for all Financial Reports and the General Ledger, but with "Create" and "Edit" disabled for all operational modules.
- The "Warehouse Manager" Role: A role with full "Create/Edit" access to Inventory and Location Transfers, but no access to Sales, Payroll, or Bank Accounts.
Enforce strict operational security with custom Roles and Permissions.