Company philosophy: The Q.wiki aims to make organizational information transparent and accessible within the company and therefore deliberately does not focus on hiding content.

However, if content should only be visible to certain people, a new web can be created for this content and provided with the appropriate rights settings (instructions for creating new web in the Q.wiki). 

If this procedure is not possible, individual pages can also be provided with rights. Below is a list of the risks that can arise when assigning rights at the page level, followed by the technical implementation.

Risks of assigning rights on pages

• Q.wiki does not provide an overview of the visible protected pages, nor does it offer a global possibility to maintain the rights settings. The maintenance effort therefore increases with each additional view-protected page.
• If the user clicks on a link of a page that is visible to him, he receives the message that he does not have the necessary rights to display it. This message is often understood as an error of Q.wiki, because users do not expect 'secret' content in Q.wiki.
• The rights settings are only effective for the page on which the restrictions are made. There is no inheritance of rights.
• Whether rights settings are applied can only be checked by a user who does not have access to the protected page.

Procedure for assigning rights on pages

Important: Only Key users, module responsible and page responsible may perform the following steps.

1. Create a group with users who should see the page in the future (instructions for group management). It is important to note that in a two-step approval workflow, the page owner and a person from the 'QMGroup' must be part of the group, otherwise the workflow will no longer work. In a one-step approval workflow, the page owner is sufficient as part of the group.
2. Open up the page and go to (three dot menu > Page access).
   Default page permission setting:
   
3. In the dialog box, you now assign “Exclusive Rights.” This means that as soon as you replace “All” with another group, all other groups are effectively excluded. This may exclude the page manager and the QM group! This makes your approval workflow no longer feasible.
   
   Please note: A maximum of 20 groups can be stored here.
   

   
   

4. With this setting, key users and the QM group can view/find the page. If the person responsible for the page is not part of one of the groups, the page is blocked for them. Close the dialog box with Save and release the page.
   
   

A test of the conversion is recommended and must be done with an unauthorized person. This person must not have access to the visible protected page. If the configured group name of the page setting does not correspond to the group name in the group management, all users are locked out of the page. A correction can only be made via the service.

When restricting rights, it may make sense not to direct the page through the sharing process in the future (instructions to remove the approval workflow from Q.wiki pages).