Policies

The Policies plugin provides a new user sign-on process, with ability to define multiple policies (site, privacy, third party), track user consents, and manage updates and versioning of the policies.

The Policies plugin forms part of Moodle’s privacy feature set and will assist sites to become GDPR compliant. It requires Moodle 3.4.2 onwards, and is available from the Moodle plugins directory. The plugin will be integrated in the Moodle 3.5 release in May 2018. Moodle 3.4.2 also includes the option of checking whether a new user is a minor.

Enabling the policies plugin

After installing the policies plugin, it may be enabled as follows:

1. Go to 'Policy settings' in the Site administration.
2. Set the Site policy handler to 'Policies (tool_policy)'.
3. Save changes.

Two new pages will then appear in the Site administration - 'Manage policies' and 'User agreements'.

Note that when Policies is set as the site policy handler, the settings 'Site policy' and 'Site policy for guests' are ignored.

Adding and managing policies

Policies and agreements

An admin or any user with the Manage policies capability (by default manager) can access the page 'Manage policies' in the Site administration and:

• Add a new site / privacy / third parties / other policy for all users, authenticated users or guests
• Change the active / inactive status of each policy
• View the number and percentage of users who have agreed to each policy
• Edit a policy and specify whether it is a minor change (not requiring users to reconfirm their consent) or not
• View the current version of each policy and also previous versions
• Change the order in which policies are shown to users

To add a new policy:

1. Go to 'Manage policies' in the Site administration.
2. Click the button 'New policy'
3. Complete the form and save changes.

Note that once created, a policy can be edited, or set to inactive, but if users have agreed to it, it can't be deleted.

Giving consent to policies

Giving consent to policies

All users (with the exception of admins) will be required to give their consent to all policies defined either for “Authenticated users” or for “All users” before proceeding further on the site.

If a new policy is added, all users will be required to give their consent when they next log in. Similarly, if an existing policy is edited and is not marked as a minor change, all users will be required to give their consent when they next log in.

If self-registration is enabled on the site, new users will be required to give their consent to all policies before proceeding to the sign-up form. If digital age of consent verification (a new setting in Moodle 3.4.2 onwards) is enabled in 'Privacy settings' in the Site administration, when a new user clicks the 'Create new account' button, they will be prompted to enter their age and country. If the user's age is lower than the age of consent for their country, they will see a message prompting them to ask their parent/guardian to contact the support contact (as specified in 'Support contact' in the Site administration).

Minors and prohibiting them from agreeing to policies

By default, the capability Agree to policies is allowed for the authenticated user role. However this capability may be prohibited for 'minors' i.e. users who are below the age of digital consent. If a user does not have the capability to agree to policies, they will be prevented from proceeding further on the site until someone can give consent on their behalf.

Sites with minors as the majority of users

To prohibit users from agreeing to policies because they are a minor:

1. Go to 'Define roles' in the Site administration.
2. Edit the role of authenticated user and set Agree to policies to prohibit.
3. Save changes.

To enable teachers and other users who are not minors to agree to policies:

1. Go to 'Define roles' in the Site administration.
2. Click the button 'Add a new role'.
3. Give the role a name such as 'Able to give consent', short name and description.
4. For context types where this role may be assigned, tick system.
5. Enter policy in the filter box, then allow the capability Agree to policies.
6. Click the button 'Create this role'.
7. Go to 'Assign system roles' in the Site administration.
8. Choose the 'Able to give consent' role to assign.
9. Select teachers and other users in the Potential users list, and use the left-facing arrow button to add them to the Existing users list.

Sites with only a few minors

To prohibit users from agreeing to policies because they are a minor:

1. Go to 'Define roles' in the Site administration.
2. Click the button 'Add a new role'.
3. Give the role a name such as 'Digital minor', short name and description.
4. For context types where this role may be assigned, tick system.
5. Enter policy in the filter box, then prohibit the capability Agree to policies.
6. Click the button 'Create this role'.
7. Go to 'Assign system roles' in the Site administration.
8. Choose the 'Digital minor' role to assign.
9. Select minors in the Potential users list, and use the left-facing arrow button to add them to the Existing users list.

User agreements

User agreements filtered to show minors

An admin or any user with the View user agreements reports capability (by default manager) can access the page 'User agreements' in the Site administration and:

• View user consents
• Filter by policy, permission, status or role
• Give consent on behalf of minors
• Download table data

For example, you can obtain the list of minors by filtering by 'Permission: Can not agree', then give consent to policies on their behalf.

User agreements for a particular policy may also be viewed via the 'Manage policies' page by clicking the link in the Agreements column.

Capabilities

• Agree to policies - allowed for authenticated user role
• Manage policies - allowed for default role of manager only
• Manage privacy settings - allowed for default role of manager only
• View user agreements reports - allowed for default role of manager only
• Agree to policies on someone else's behalf - allowed for default role of manager only

See also

• GDPR for administrators (Moodle 3.4.2+)