[wp-trac] [WordPress Trac] #44176: Un-map Privacy Capabilities

[WordPress Trac]

#44176: Un-map Privacy Capabilities
-------------------------------------------------+-------------------------
 Reporter:  desrosj                              |       Owner:  xkon
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Privacy                              |     Version:  4.9.6
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-screenshots needs-     |     Focuses:  multisite
  dev-note has-unit-tests needs-refresh          |
-------------------------------------------------+-------------------------

Comment (by nedmartin.org):

 May I point out that this should be the other way around?

 By default, a new site should allow the editor to edit the privacy page,
 but the permissions should exist to prevent an editor from doing so if
 someone wishes to customise it.

 The reasoning for this is simple: Most WordPress sites are used by
 organisations who are not large enough to have separate DPO accounts
 designated to edit a single privacy policy page, they will likely just
 have 1 admin user who is a developer (and not in a position to edit
 pages), and 1 or 2 editors and maybe some authors.

 The majority of users should not be limited by a new choice such as this.

 If the organisation is large enough to have dedicated user roles for
 managing privacy policies, then that organisation is also large enough to
 change the default setting to restrict access to editing the privacy
 policy page.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/44176#comment:67>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform