[wp-trac] [WordPress Trac] #38298: Multiple role assignments and separation of development and operation roles

WordPress Trac noreply at wordpress.org
Wed Oct 12 23:23:02 UTC 2016


#38298: Multiple role assignments and separation of development and operation roles
-----------------------------+-----------------------------
 Reporter:  galbaras         |      Owner:
     Type:  feature request  |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Role/Capability  |    Version:  4.6.1
 Severity:  normal           |   Keywords:
  Focuses:  administration   |
-----------------------------+-----------------------------
 WordPress currently only allows the assignment of one role to a user and
 the default roles are organized hierarchically, with each one being a
 superset of the next, up to the almighty administrator role.

 However, development is only possible for administrators, so there is no
 role that allows operational administration (user management, comment
 approval, etc), but no development capabilities, (theme settings, widgets,
 plugins, custom CSS, etc).

 I think there is a need to separate these things, and the best way to do
 this is to create a "Developer" role, and perhaps a "Customizer" role,
 which can be assigned to certain administrators. Since presentation
 capabilities are on a different dimension from content/operation
 capabilities, there is a need to assign them to users in parallel.

 For example, the proposal for custom CSS in the customizer introduces a
 way for people who don't know what they're doing to cause display
 problems. By assigning to them a role that allows operational
 administration, but no development capabilities, this function can be
 reserved for the knowledgeable users only.

 Allowing multiple role assignment may be a big change, but it's likely to
 be useful to many people, because without it, professionally supported
 sites end up giving client employees more power than they should have.

 I know there are plugins for these things, but I think they should be in
 core, and leave the plugins to handle uncommon situations.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/38298>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list