Skip to main content

Understanding Access in SimplerQMS

Ensure each user can only perform actions aligned with their responsibilities by combining license-based roles with module-level permissions.

Who Is This For?

  • QA Administrators / System Admins — configuring licenses, modules, and governance

  • People Managers / Process Owners — deciding who needs access to what

  • Power Users / SMEs — validating access against operational needs

How to Do It?

Step 1: Understand the two-tier access model

SimplerQMS controls access at two levels that work together:

  • User roles (license type) – broad capabilities (Full, Standard, Light, Free)

  • Module-based permissions – fine-tuned access to product areas (e.g., Document Control, Change Control, Training)

Compliance reminder: Grant the minimum necessary access to perform job duties (least privilege).


Step 2: Review user license and module-based permissions

License Types

User roles are tied to license types in SimplerQMS, and each license type unlocks specific capabilities. The table below outlines the access granted based on each license type:

Product Area

Action

Full

Standard

Light

Viewer

Document Control

Create and edit documents

x

x

Sign & Approve documents

x

x

x

Change Control

Create and edit change requests

x

x

Sign & Approve change requests

x

x

x

Training

Create and edit Training rules

x

(x)

Complete Training (Read & Sign)

x

x

x

Actions

Create & Complete Actions

x

x

x

Search & View

Search and view documents & records

x

x

x

x

Analytics

View analytics data and reports

x

(x)

Settings

Create & Manage Types, Processes, Tags, Change Control Settings

(x)

(x)

(x)

📝 Notes:

  • Settings visibility depends on specific admin permissions assigned to the user or group.

  • Licenses can be managed by the your designated SimplerQMS administrators. These administrators can change the users license type (if there is a promotion/demotion) and reassign the two (2) additional flex modules that each Standard user is assigned.

Module-Based Permissions

Modules refine what a user actually sees and can do inside the app—even with a Full license.

  • Document Control – allow Create/Edit documents

  • Change Request – allow Create/Edit change requests

  • Training – allow View/Create/Edit training records

  • Analytics – allow viewing dashboards and reports

💡 Note: Both License Type and Module Permissions can be configured under Settings → Users, and only the Administrator has access to do so.


Tips

  • 💡 Apply least privilege: start restrictive and add access only when justified.

  • 💡 Re-check access after role changes (promotion, department move, project assignment).

What’s Next?

Did this answer your question?