Skip to content
QTO ERP Docs
Try QTO ERP for FREE

Permissions and Page Access

QTO ERP uses two layers of access control:

  • Standard permissions for records and actions.
  • Deep permissions for page structure, navigation, fields, buttons, row actions, and data scopes.

The Deep Permissions service supports:

Area What can be configured
Apps Whether a module/app is available.
Header pages Top-level pages inside an app.
Subheader pages Nested pages or sections.
Page sections Groups of fields or interface areas.
Fields Field visibility and field-level access.
Buttons Action buttons on pages.
Highlights Summary cards or KPI-style values.
Filters Filter controls on list pages.
Columns Table columns.
Row actions Per-row actions in tables.
Data scope Whether a user sees own, team, department, or all records where supported.

Designation permissions and user overrides

Section titled “Designation permissions and user overrides”

Deep permissions can be assigned by designation. User overrides can then adjust access for a specific user.

The implementation includes CRUD endpoints for designation permissions and user overrides across apps, headers, subheaders, sections, fields, buttons, highlights, filters, columns, row actions, and data scopes.

The system can resolve a user’s effective permissions for a page by combining designation permissions and user-specific overrides.

This is why two users with similar job titles may see different page sections, fields, buttons, or table actions.

  • Superusers can bypass ordinary permission checks.
  • Some frontend configuration treats an empty permission list as superuser-only.
  • Business rules can still block an action even when a user can see the button.
  • Module docs should avoid fixed role matrices unless product confirms role names and assignments.