Policies
Maintained by
Sara Arjona, Moodle HQ
Allows to define various policy documents - site policy, privacy policy, intellectual property policy, late assignments policy and others as needed. It keeps the history of document revisions, tracks user agreements with them and forces
users to accept them prior to using the site.
Comments
Comments are no longer open for new posts. Existing comments remain available to read.
For now it's not possible to be done via CSV or bulk action. But maybe you can use some "Checkbox cheker" browser extension (such as the CheckThemAll for Firefox https://addons.mozilla.org/en-GB/firefox/addon/checkthemall) for selecting all them easily
Cheers!
Unfortunately this is not really what I need - what I could find is that I need to select all users one by one to save the consent for them - but for 5000 users it would take an eternity.
Could this be done by CSV upload or with the "bulk actions"?
Thanks,
Gabor
You'll find the answer on the following page: https://docs.moodle.org/35/en/Policies_plugin#Giving_consent_on_behalf_of_multiple_users
Hope this helps!
Is it possible somehow to accept policies for a large number of users as an admin?
I want to change the default (core) policy handler to this tool_policy, but I would like to set existing users who already gave consent for the new plugin as well.
Thanks in advance!
Current policy tool version doesn't allow this. For now, all the policies are displayed to all the users and the only kind of audience you can choose when creating a new policy is "All users", "Authenticated users" or "Guests". As you can see, there isn't anything related to roles or other user profile fields. If you feel this could interest other users, you could create a new issue on the tracker. If you haven't done before, you will find more information about the issues creation here: https://docs.moodle.org/dev/Tracker_guide#When_creating_an_issue
Cheers!!
Thanks
Nick
Cheers,
Ray
Cheers!!
For simplicity, it would probably be easier to add the capability to choose it by cohort or group.
Thanks again for this plugin!
@Salvador - Sorry I noticed there is a typo in my previous comment. The time-to-live of that cache is 1800 seconds which indeed is 30 minutes and not 3 minutes.