Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-63013

Allow terms and conditions to be agreed to before showing the privacy statement.

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.6
    • Fix Version/s: 3.6
    • Component/s: Privacy
    • Labels:
    • Testing Instructions:
      Hide
      1. Log in as admin
      2. Go to Site administration > Users > Privacy and policies > Policy settings
      3. In the "Site policy handler" dropdown, select "Policies (tool_policy)", then click "Save changes".
      4. Go to Site administration > Users > Privacy and policies > Manage policies
      5. Define 4 policy documents, with policy status set to active. For two of them, set "Show policy before showing other policies" to "Yes", for the rest leave it to "No".
      6. Log out.
      7. Log in as a student.
      8. TEST: Policies that are to be shown before other policies should behave so: they must be shown first and each of them has to be accepted to allow the user to continue.
      9. TEST: Only after all such policies are accepted, the remaining policies are shown and finally have to be accepted on the final consent page.
      10. TEST: Once all policies are accepted, the user can use the site.
      11. Log in as the admin again.
      12. Go to Site administration > Plugins > Authentication
      13. In the "Self registration (registerauth)" setting, choose "Email based registration"
      14. Log out
      15. Go to the login screen and attempt to create a new account
      16. TEST: Make sure the behaviour is consistent: Policies that are to be shown before other policies, are shown first.
      Show
      Log in as admin Go to Site administration > Users > Privacy and policies > Policy settings In the "Site policy handler" dropdown, select "Policies (tool_policy)", then click "Save changes". Go to Site administration > Users > Privacy and policies > Manage policies Define 4 policy documents, with policy status set to active. For two of them, set "Show policy before showing other policies" to "Yes", for the rest leave it to "No". Log out. Log in as a student. TEST : Policies that are to be shown before other policies should behave so: they must be shown first and each of them has to be accepted to allow the user to continue. TEST : Only after all such policies are accepted, the remaining policies are shown and finally have to be accepted on the final consent page. TEST : Once all policies are accepted, the user can use the site. Log in as the admin again. Go to Site administration > Plugins > Authentication In the "Self registration (registerauth)" setting, choose "Email based registration" Log out Go to the login screen and attempt to create a new account TEST : Make sure the behaviour is consistent: Policies that are to be shown before other policies, are shown first.
    • Affected Branches:
      MOODLE_36_STABLE
    • Fixed Branches:
      MOODLE_36_STABLE
    • Epic Link:
    • Pull from Repository:
    • Pull Master Branch:
      MDL-63013-master-prioritypolicy
    • Sprint:
      GDPR Followup Sprint 1

      Description

      It is demanded to have a feature that the user has to agree to the terms and conditions statement first prior going through the rest of policies acceptance workflow. This requirement follows on from the initial mock-up:

      The basic use case comes from uni's (or other organisations) wanting a user to first sign off on the site terms and conditions, as a contract of use for the site. If the user doesn't want to sign off on this then they won't be allowed access to the site (no matter what), and there is no point at all in proceeding to show them privacy statements (why waste their time?).

      So, in more 'user story-like' language:

      As an admin I need my users to agree to the site T&Cs as a contract and their agreement of use, before proceeding with any other sign on functionality as without their agreement to the T&Cs they will not be allowed on the site.

      This is also a way to more formally separate the T&Cs from privacy statements - they have different purposes.

        Attachments

        1. 1.PNG
          1.PNG
          91 kB
        2. 2.PNG
          2.PNG
          101 kB
        3. screenshot-1.png
          screenshot-1.png
          111 kB

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  3/Dec/18

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 14 minutes
                  14m