Make WordPress Core

Opened 6 years ago

Last modified 4 years ago

#43821 new enhancement

Add UX in the Network Admin for setting a network-wide privacy policy

Reported by: coreymckrill's profile coreymckrill Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: Privacy Keywords: privacy-roadmap needs-design has-screenshots
Focuses: multisite Cc:


Some multisite instances will need to set one privacy policy for the entire network, with controls on whether or not individual sites can modify/replace it. Other multisite instances may choose to leave the privacy policy entirely to individual sites.

The UI for setting a network-wide policy should probably be similar to #43435, so snippets from plugins can be included.

Attachments (1)

My-Sites-Settings-screen.png (135.2 KB) - added by paaljoachim 4 years ago.
Going to My Sites -> Settings shows the following Network Settings screen.

Download all attachments as: .zip

Change History (17)

#1 @iandunn
6 years ago

Related: privacy_policy_url filter proposed in ticket:43620#comment:30.

#2 @iandunn
6 years ago

Relevant feedback from @flixos90 on #43935

I like the capabilities approach, however I think we shouldn’t assume that a network works that way that it has a single privacy policy. I‘d prefer if we introduced an extra setting toggle in the network admin like “Restrict privacy policy management to network administrators?”. Only if that is checked, the capability should be restricted from regular administrators. We could even add a “Use a network-wide privacy policy?” toggle and if that is set, provide a UI in the network admin and then override what’s set per single site, like several other network settings work. The current solution is fine though as first step though, especially since Beta is tomorrow.

This ticket was mentioned in Slack in #core-multisite by iandunn. View the logs.

6 years ago

#4 @desrosj
6 years ago

  • Component changed from General to Privacy

Moving to the new Privacy component.

This ticket was mentioned in Slack in #gdpr-compliance by desrosj. View the logs.

6 years ago

#6 @desrosj
6 years ago

  • Keywords ux-feedback added
  • Milestone changed from Awaiting Review to Future Release

#7 @allendav
6 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.

#8 @desrosj
6 years ago

  • Keywords privacy-roadmap added

#9 @desrosj
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 #design by boemedia. View the logs.

5 years ago

#11 @garrett-eclipse
5 years ago

  • Keywords needs-design added; ux-feedback removed

This will need a design before feedback can be provided. Switching the keyword ux-feedback for needs-design

#12 @garrett-eclipse
4 years ago

  • Milestone changed from Future Release to 5.5

This ticket was mentioned in Slack in #core by david.baumwald. View the logs.

4 years ago

#14 @mapk
4 years ago

  • Keywords needs-screenshots added

4 years ago

Going to My Sites -> Settings shows the following Network Settings screen.

#15 @davidbaumwald
4 years ago

  • Keywords has-screenshots added; needs-screenshots removed

#16 @davidbaumwald
4 years ago

  • Milestone changed from 5.5 to Future Release

With 5.5 Beta 1 releasing tomorrow ans this still needing a refresh and a review, 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.

Note: See TracTickets for help on using tickets.