mahara-contributors team mailing list archive

[Kristina Hoeppner <1734174@xxxxxxxxxxxxxxxxxx>]

changed the wording to mean "privacy statement" in the description
rather than T&C as that is the immediate change that is required.

** Summary changed:

- Re-trigger consent and agreement to T&C when they change or when user changes institutions
+ Re-trigger consent to privacy statement when they change or when user changes institutions

** Description changed:

  We need to make a series of changes in Mahara to comply with the GDPR.
  More info is available on the wiki at
  https://wiki.mahara.org/wiki/Developer_Area/Specifications_in_Development/GDPR_compliance
  
- The following should be possible (note: T&C refers to the general
- agreement and also any specific explicit consent):
+ The following should be possible:
  
- 1. When site T&C change, user needs to accept them again.
- 2. When institution T&C change, user needs to accept them again.
- 3. When user joins a new institution, they need to agree to the new institution's T&C.
+ 1. When site privacy statement changes, user needs to accept it again.
+ 2. When institution privacy statement changes, members of the institution need to accept it again.
+ 3. When user joins a new institution, they need to agree to the new institution's privacy statement.
  
- If only site or institution T&C change, the user should still be
- presented with all T&C but it should be clear which section has changed,
- e.g. show the institution T&C in a non-retracted panel but the site T&C
- in a retracted panel so they can read them again, but it's clear which
- section needs approval.
+ If only site or institution privacy statement changes, the user should
+ still be presented with the site and institution privacy statement but
+ it should be clear which section has changed, e.g. show the institution
+ privacy statement in a non-retracted panel but the site privacy
+ statement in a retracted panel so they can read them again, but it's
+ clear which section needs approval.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1734174

Title:
  Re-trigger consent to privacy statement when they change or when user
  changes institutions

Status in Mahara:
  Confirmed

Bug description:
  We need to make a series of changes in Mahara to comply with the GDPR.
  More info is available on the wiki at
  https://wiki.mahara.org/wiki/Developer_Area/Specifications_in_Development/GDPR_compliance

  The following should be possible:

  1. When site privacy statement changes, user needs to accept it again.
  2. When institution privacy statement changes, members of the institution need to accept it again.
  3. When user joins a new institution, they need to agree to the new institution's privacy statement.

  If only site or institution privacy statement changes, the user should
  still be presented with the site and institution privacy statement but
  it should be clear which section has changed, e.g. show the
  institution privacy statement in a non-retracted panel but the site
  privacy statement in a retracted panel so they can read them again,
  but it's clear which section needs approval.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1734174/+subscriptions