Opened 7 years ago
Last modified 4 years ago
#43822 new enhancement
Add UX in the Network Admin for exporting/anonymizing/deleting personal data across the entire network
Reported by: | coreymckrill | Owned by: | |
---|---|---|---|
Milestone: | Future Release | Priority: | normal |
Severity: | normal | Version: | |
Component: | Privacy | Keywords: | privacy-roadmap needs-patch |
Focuses: | multisite | Cc: |
Description
It's not practical for a super admin to hunt down personal data by going to the Dashboard of each site in the network. There should be one centralized place in the Network Admin to receive and process SARs.
This should look similar to the UX in #43546 and #43602, but the underlying functionality for managing the data across the entire network is being discussed in #43738.
Change History (14)
This ticket was mentioned in Slack in #gdpr-compliance by desrosj. View the logs.
7 years ago
#5
@
7 years ago
The solution will need to take into account mu-plugins / plugins that are used on all the sites vs plugins that are installed on individual sites. The exporters and erasers can vary from site to site.
#8
@
6 years ago
- Keywords gdpr removed
Removing the GDPR keyword. This has been replaced by the new Privacy component and privacy focuses in Trac.
This ticket was mentioned in Slack in #core-privacy by pbiron. View the logs.
5 years ago
This ticket was mentioned in Slack in #core by david.baumwald. View the logs.
4 years ago
#14
@
4 years ago
- Milestone changed from 5.5 to Future Release
With 5.5 Beta 1 releasing tomorrow, this is being moved to Future Release
. If any maintainer or committer feels the remainder of this ticket can be resolved in time, or wishes to assume ownership during a specific cycle, feel free to update the milestone accordingly.
I wonder if there are use cases where the network admin will want to delegate this to single site admins. For instance, an agency that has a multisite instance for all of their clients. The sites are completely unrelated to one another, and the individual site admins would be the most appropriate people to respond to SARs, rather than the network admin.
The
wp_users
table is shared, though, so that's a complication. Maybe v1 just has the network admin doing everything, and future iterations can consider adding granularity?