Search documentation

Search pages and sections of the Rona docs

Back to homeDocs Hub

Getting Started

  • Introduction
  • Setup
  • First Steps
  • Dashboard

Core Modules

  • Inventory
  • Sales
  • Manufacturing
  • Quality
  • Traceability
  • Finance
  • Workforce
  • Kiosk

Admin & Permissions

  • Users
  • Roles
  • Organization
  • Audit Logs

Rona AI

  • Overview
  • Queries
  • Reports
  • Tracing

API Reference

  • Authentication
  • Inventory API
  • Sales API
  • Manufacturing API
  • Finance API

Version

v2.6 · Real-time lot tracing

Admin & Permissions / 02

Roles and Permissions

Roles and permissions control what users can do in Rona ERP. Role-based access control (RBAC) ensures users only have access to the features they need — following the principle of least privilege.

RBACLEAST PRIVILEGECUSTOM ROLES

Key concepts

  • Roles group permissions together
  • Users can have multiple roles
  • Permissions are granular actions (read, create, update, delete)
  • Permissions are module-specific (e.g., inventory.item.read)
  • Follow the principle of least privilege
  • Custom roles can be created for specific needs

Default roles

Admin

Full access to all features and system settings. Can create users, manage roles, and configure organization settings. Limit to trusted personnel.

ALL MODULE PERMISSIONSUSER MANAGEMENTORG SETTINGSAUDIT ACCESS

Manager

Full access to operational features but no system administration. Can manage day-to-day operations but cannot change system configuration or user access.

ALL MODULE PERMISSIONSNO USER MGMTLIMITED AUDIT

Operator

Limited to specific operational tasks. Can perform day-to-day work but cannot make strategic decisions or access sensitive data.

READ + CREATELIMITED UPDATENO DELETE

Viewer

Read-only access to most features. Can view data and reports but cannot make changes — useful for auditors, executives, or external stakeholders.

READ ONLYREPORTSDASHBOARDS

Permission structure

Permission format
module.entity.action

module    →  which module (inventory, sales, manufacturing, ...)
entity    →  which entity (item, order, batch, ...)
action    →  what action (read, create, update, delete)
Examples
inventory.item.read           View items
inventory.item.create          Create new items
inventory.item.update          Modify existing items
inventory.item.delete          Delete items
sales.order.read               View sales orders
sales.order.create             Create sales orders
manufacturing.batch.read       View production batches
finance.invoice.issue          Issue invoices

Custom roles

Create custom roles with specific permission combinations when default roles do not fit — department-specific roles, external partners with limited access, or compliance-driven permission sets.

Example — Quality Manager
Quality moduleFull permissions (read, create, update, delete)
Inventory moduleRead-only — to view lot status
Manufacturing moduleRead-only — to view batch status
Other modulesNo access

Assigning roles

  • Assign the minimum roles needed for the job
  • Review role assignments regularly
  • Remove roles when job responsibilities change
  • Document role assignment rationale
  • Avoid role proliferation (too many custom roles)

Principle of least privilege

Always assign the minimum permissions needed for a user to perform their job. This reduces security risk and limits the potential impact of compromised accounts.

Permission enforcement

Defense in depth
Frontend UIButtons and forms hidden based on permissions
Backend APIControllers check permissions before executing
DatabaseRow-level security (RLS) enforces tenant isolation

Auditing role changes

Logged events
Role lifecycleRole creation and modification
PermissionsPermission assignment to roles
AssignmentRole assignment to users
RemovalRole removal from users
AccountabilityWho made the change and when
Continue

Organization settings

Branding, currency, VAT, branches, and platform configuration.

Organization settings
PreviousUsersNextOrganization