Skip to content
QTO ERP Docs
Try QTO ERP for FREE

Roles & Permissions

QTO ERP uses a dynamic permission model. It does not rely on one fixed role matrix for every customer or team. A user’s access depends on their account permissions, group membership, designation, superuser/staff status, and any deeper page-level rules configured for the relevant module.

  • Users and groups: users can receive permissions directly or through groups.
  • Standard record permissions: many records use separate permissions for view, add, change, and delete actions.
  • Custom permissions: modules add business-specific permissions such as viewing all records, viewing team records, approving leave steps, or accessing special workflows.
  • Superuser access: superusers bypass normal permission checks and can see pages that are otherwise hidden.
  • Authentication checks: protected areas require the user to be signed in.

The frontend loads the signed-in user’s permissions and filters the workspace from that list. Modules, header pages, and subpages are only shown when the user has at least one required permission for that item.

Examples verified in the current navigation include:

  • Attendance pages require attendance, leave, or organization permissions.
  • Salary pages require payroll permissions such as salary record, salary profile, or income tax permissions.
  • Careers pages require job portal permissions such as requisition, job, or job application permissions.
  • Project Management pages require project management permissions.
  • Accounts pages require accountant permissions for accounting records and payroll configuration.

If a page has no permission requirement configured, the current shell treats it as superuser-only.

QTO ERP also supports deeper UI permissions. These can control:

  • Page sections
  • Individual fields
  • Page buttons
  • Row actions such as view, edit, delete, inline edit, modal actions, or API actions
  • Dashboard highlights
  • Filters
  • Table columns

This means a user may be able to open a page but still not see every field, button, column, or row action on that page.

Some areas use data scopes to limit which records a user can see. The verified scopes are:

Scope Meaning
Own records The user sees records connected to them.
Team records The user sees their own records plus subordinate or team records where supported.
Department records The user sees records connected to their department where supported.
All records The user can see all records for that page or workflow.

Task and project-related permissions use these scopes in several places. Account and activity-log views also include own, team, and all-style restrictions based on permissions such as team or all access.

The implementation supports reporting-line and team-aware access. For example, team-based account and activity views include the user plus subordinates. Task and project data can also be filtered by own, team, department, or all scope.

Administrative users can manage broader configuration depending on their permissions. This includes users, groups, permissions, navigation/page permissions, page structure, buttons, fields, data scopes, system settings, and module configuration.

Do not assume a page is available to every user with the same job title. In QTO ERP, available pages, visible actions, editable fields, reports, and data scope depend on the permissions assigned to that specific user or group.