← Back to team overview

mahara-contributors team mailing list archive

[Bug 1734178] Re: Everybody should be allowed to delete their account themselves

 

** Tags added: nominatedfeature

-- 
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/1734178

Title:
  Everybody should be allowed to delete their account themselves

Status in Mahara:
  In Progress

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

  Currently, only when self-registration is turned on can users delete
  their account. This should be possible for anyone though also for
  those from external authentication methods or those that had accounts
  created manually in institutions where self-registration is not
  allowed.

  Sometimes, institutions may like to keep certain student content (upon
  agreement) and thus account deletion could not be good if the student
  hadn't already transferred their content to an area where it can be
  retained.

  Therefore, it might be good to implement a "Review account before
  self-deletion" option in an institution. This could work the following
  way:

  1. User clicks the "Delete" button and is informed that the admin receives a notification and will need to approve the deletion. They'd also get the general warning that all their content in their personal portfolio area will be deleted but that group content stays, but is not associated with their name anymore.
  2. In their account settings page they'll see when they triggered the deletion and if they don't receive a message, can re-trigger it and append a message to the institution admins.
  3. The request for deletion triggers a notification to the institution admins (or site admin if there is no institution admin) letting them know about this action. They can then approve the deletion or deny it and provide a mandatory reason so that the student can get in touch with them and discuss the deletion.

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


References