PolicyConnect Administrators can secure their user generated modules by following these steps:

1. Send a Service Desk request asking for the Secure User Generated Module feature to be switched on.

2. Once activated, access permissions are required to allow users to access the secure module. These permissions are to be created within your identity solution software, this may be Single Sign-On or User Directory.

2a For Single Sign-On, your internal IT team will need to create the permission and allocate it to people who require it, however you will still need to let the Service Desk Agent know which SSO groups have been allocated these permissions.

2b For User Directory, please let the Service Desk agent know what you would like the permission naming to be and the agent will request our technical team to set this up.

Important Notes:

• It is important that staff are given the required permission rights before the module is secured, if you want staff other than yourself to be able to access the module.
• The above steps MUST be completed in order for the securing of your UGC content to be successful.

4. Ensure that you are in Administrator View

5. Click the Gear in the top menu. This will take you to Settings.

6. Select Content Admin in the left menu. This will take you to the Manage My Content Page.

7. Click the padlock next to the user generated module you would like to secure.

8.  Click the white slider next to Secure, which will then turn green.

Important Note: For group/parent sites, securing or un-securing a module will apply to child sites as well. This means that all child sites which have this module activated will only be able to edit/view the module if they have the required permissions configured. 

9. Add the permission group name in the space provided (see example image below). This permission group name will be used to provide users with access to this module and it must exactly match the permission group name that has been set up in your identity software. It must include the 'pc_' section at the beginning of the name otherwise it will not work.

• Important note for special characters: the permission group name can include letters, underscore, space and hyphen.

Note: It is not mandatory to add a permission group when securing a module, however, if you do not add a permission group when securing a module, only the PolicyConnect administrator will be able to see this module. To remove this, the administrator will need to 'unsecure' the module by unlocking the padlock and saving. 

10. Click Save

The existing Edit/View permissions for PolicyConnect will remain:

• For a person to have editing permissions for this secure User Generated module, they will require the following permission groups: PolicyConnect Administrator (or however your Administrator group is named) and 'Module permission group name'
• For a person to have general user access for this secure User Generated module, they will require the following permission groups: PolicyConnect User (or however your General user group is named) and 'Module permission group name'

11. Once user authentication configuration is complete the module is now secure and only those users who have been added to that permission group will be able to view/edit the module.