Roles & permissions¶

In one sentence: Every user has one main role, which sets how much they can do. They can also hold function roles (such as "CIRS Officer"), which add rights for one special area.

The six main roles¶

From most to least powerful:

Role	Who is it?	Scope	In short
RiQS Administrator	The RIQS platform team	All organisations	Creates organisations, supports clients, and is the only role that can delete in audit-safe mode
Group Administrator	Client admin for a group of organisations	All organisations in the group and their units	Manages several organisations at once
Administrator	Client admin for one organisation	Own organisation and all its units	Sets up units, users, subscription and organisation-wide settings
Power User	Lead of a unit	Own unit (or several, if given)	Manages the unit: users, content, plans and officers
Management	Unit management	Own unit	Mostly reads and runs daily operations. Fewer setup rights than a Power User
Professional	Regular staff member	Own unit	Does the daily work: reads, fills in, completes and reports

Older names you may still hear: Professional was called Employee A. The role Employee B has been removed.

Simple rule of thumb¶

Set up and configure → Administrator / Power User
Plan and follow up → Power User / Management
Do and report → Professional (and everyone else)

Function roles (added on top of a role)¶

A function role gives one person extra rights for one area without changing their main role. For example, a Professional can be the unit's Fault Officer.

Function role	Responsible for	Details
CIRS Officer	Reviewing and handling critical incident reports	Incident Reports
Complaint Officer	Handling complaints	Incident Reports
Ideas Officer	Reviewing improvement ideas	Incident Reports
Feedback Officer	Handling employee feedback	Incident Reports
Fault Officer	Handling fault reports and fault groups	Incident Reports
Hint Officer	Handling hints	Incident Reports
Equipment Officer	Looking after devices and their maintenance	Equipment
RiQS-Pedia Officer / Unit Manager / Organisation Manager	Managing folders and documents, approvals and templates in the library	RiQS-Pedia
Auditor / Committee	Reviewing and deciding in survey certification	Surveys

Officers can be set per unit or for the whole organisation, depending on the module.

Who can manage users and roles?¶

This is a summary based on the official role sheet. The Users page has the full table.

Action	RiQS Admin	Group Admin	Admin	Power User	Management	Professional
Create and invite users, edit user data	✅	✅	✅	✅	✅	❌
Activate / deactivate users	✅	✅	✅	✅	✅	❌
First activation of another user	✅	✅	✅	❌	❌	❌
Make someone an Administrator (must already be a Power User)	✅	✅	✅	❌	❌	❌
Make someone a Power User for one unit	✅	✅	✅	✅	❌	❌
Make someone a Power User for several units	✅	✅	✅	❌	❌	❌
Set the CIRS Officer for the organisation	✅	✅	✅	❌	❌	❌
Delete a user (regular version)	✅	✅	✅	❌	❌	❌
Delete a user in audit-safe mode after activation	✅	❌	❌	❌	❌	❌
Change own password	✅	✅	✅	✅	✅	✅

How to read the permission tables in these docs¶

Every module page has a "Who can do what" table:

✅ = allowed
❌ = not allowed
text = allowed with a condition, e.g. own unit only, only if assigned, only as Fault Officer
"Delete (regular)" and "Delete (audit-safe)" are listed separately where they differ. See Audit-safe mode.

Good to know¶

Rights always apply inside the unit you are currently in. A Power User of unit A is not a Power User of unit B unless they were given that.
If a button is missing, check three things in this order: the subscription, the user's role, and whether the item is assigned to them.

Last reviewed: 2026-10-26