You need key user rights to perform the following steps.

When a new Q.wiki user is created (either manually or via the Active Directory), he or she automatically receives the rights of a "normal user" without having to be assigned manually. The employee can then immediately start working in Q.wiki. However, you also have the following options for granting the user further rights or withdrawing rights.

Extension of rights:

• Assignment to the KeyUserGroup
• Assignment to the QMGroup
• Assignment to the ResubmissionGroup
• Assignment to the ReportingGroup 
• 
  

As a key user, you can now also see which rights your employees have in the apps via the acess overview. This means which groups have read or write permissions.

You can also make changes to the rights of your groups directly via the cogwheel of an app. 

Restriction of rights:

• Assignment to the ReadOnlyGroup

Description of the individual rights groups

Assignment of functions in the processes web to rights groups

Add user groups

• detailed instructions can be found here: Add users to Q.wiki groups

NOTE: Please assign the role of a key user carefully, because with many rights comes much responsibility. Please ensure that people are properly trained: Modell Aachen Academy.Key users can, for example, click through the approval workflow without "hurdles" (key users have the technical authorisation in their function to carry out both the content-related and the formal approval). However, this can lead to a disregard of the dual control principle and thus possibly also to a deviation in the audit. For companies with up to 200 employees, a maximum of 3 key users is recommended. These key users should only make use of their rights in the release workflow in exceptional cases, e.g. in the case of illness of a person responsible for a page. Otherwise, the content-related release is the sole responsibility of the page managers. Formal approval is traditionally carried out by the QM (= user in the QM group / max. 2 persons).