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, 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
Use this table to understand what each license enables at a high level.
Product Area | Action | Full | Light | Free |
Document Control | Create and edit documents | x |
|
|
| Sign & Approve documents | x | x |
|
Change Control | Create and edit change requests | x |
|
|
| Sign & Approve change requests | x | x |
|
Training | Create and edit Training plans | x |
|
|
| Complete Training (Read & Sign) | x | x |
|
Actions | Create & Complete Actions | x | x |
|
Search & View | Search and view documents & records | x | x | x |
Reporting | View analytics data and reports | x |
|
|
Settings | Create & Manage Types, Processes, Tags, Change Control Settings | x |
|
|
Admin Settings | Manage Users, Groups, Org (as permissions granted) | (x) | (x) | (x) |
📝 Note: Admin Settings visibility depends on specific admin permissions assigned to the user or group.
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 System Administrator has access to do so.
📎 Reference: Managing users and access
Step 3: Validate effective access (license + modules)
Confirm what a user can see/do by checking an example scenario:
A user with Full license without the Training module enabled will not see or edit training plans.
A Light license with Document Control module enabled can Sign & Approve but cannot create/edit documents.
💡 Tip: Test with a non-admin account to verify the end-user view.
Tips
💡 Apply least privilege: start restrictive and add access only when justified.
💡 Use Groups to manage modules at scale; avoid one-off user overrides.
💡 Re-check access after role changes (promotion, department move, project assignment).