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 / 01

Users and Authentication

Users are the system accounts that allow people to access Rona ERP. Each user has authentication credentials, roles that determine permissions, and can be linked to employee records.

JWTRBACSESSIONS

Key concepts

  • Users have login credentials (email/password or OAuth)
  • Roles determine what users can do in the system
  • Permissions are granular actions (read, create, update, delete)
  • Users can be linked to employee records for HR integration
  • Multi-factor authentication available for security
  • Session management with automatic timeout

User creation

User fields
EmailUnique email address, used for login
PasswordSecure password, hashed before storage
NameDisplay name
RolesOne or more roles that grant permissions
Employee linkOptional link to an employee record
StatusACTIVE or INACTIVE

Authentication methods

Supported methods
Email / passwordTraditional username and password
Google OAuthSign in with a Google account
Multi-factorAdditional security layer (optional)

User status

ACTIVEINACTIVE

Inactive users cannot log in, but their data is preserved. Deactivate users when an employee leaves, when temporary access is no longer needed, or during a security incident requiring account lockout.

User–employee link

Link benefits
AttendanceAttendance records tied to the employee
DepartmentsDepartment-based data access
IdentitySingle source of truth for user identity
ManagementStreamlined user management

Password management

Password security
HashingPasswords are never stored in plain text
Minimum lengthEnforced minimum password length
Reset flowSecure password reset via email
Session timeoutAutomatic logout after inactivity

Security best practices

  • Use strong passwords (minimum 8 characters, mix of types)
  • Enable multi-factor authentication for sensitive roles
  • Deactivate users immediately when they leave
  • Review user access regularly
  • Apply the principle of least privilege for role assignment

Session management

Session features
Automatic timeoutSessions expire after inactivity
Manual logoutUsers can log out explicitly
Session invalidationAdmins can invalidate all sessions
Remember meOptional extended session — not recommended for shared devices

User audit trail

Logged events
LifecycleUser creation and modification
RolesRole assignment changes
LoginsLogin attempts — successful and failed
PasswordsPassword changes
SessionsSession invalidation
Continue

Roles and permissions

How RBAC controls what each user can do — default roles, permission format, and least privilege.

Roles & permissions
PreviousKioskNextRoles