Skip to content
QTO ERP Docs
Try QTO ERP for FREE

Roles

QTO ERP uses several role-related concepts. They are related, but they do different jobs.

Concept Purpose
Permission Groups Bundle permissions and assign them to users. These are the main role-based access tool.
Designations Store job titles and optional role slugs used by workflow logic.
Organization Teams Group users for operational work and team-level visibility.
Superuser Bypasses ordinary permission restrictions.

Permission groups have a name, assigned permissions, and users.

Available actions include:

  • Create, update, and delete groups.
  • Add permissions to a group.
  • Remove permissions from a group.
  • Replace all permissions on a group.
  • View users in a group.
  • Add users to a group.
  • Remove users from a group.
  • View group statistics.

Designations represent job titles or business roles. They include name, description, active status, optional role slug, and employee count.

Designations can be used with employee records and may map to workflow role behavior in parts of the system.

Organization teams are separate from permission groups. A team belongs to an organization and may be scoped to a department, office, organization, or cross-department structure.

Team memberships include a role such as member, team head, reviewer, observer, or another configured team role. A user can have only one active membership for the same team.

Role and group management is controlled by standard permissions, such as view, add, change, and delete permissions for groups, permissions, designations, teams, and team memberships.

  1. Open the role or group management area available to administrators.
  2. Create a group with a clear name.
  3. Add the required permissions.
  4. Add the intended users.
  5. Ask users to reload or sign in again if navigation does not update immediately.
  6. Review activity logs if you need an audit trail for the change.
  • Group names must be unique.
  • Permission IDs must refer to real permissions.
  • User assignments must refer to real users.
  • Team memberships prevent duplicate active membership for the same user and team.

Do not treat job titles as a complete permission model. Effective access comes from permissions, groups, superuser status, and record-level scope.