Opened 4 years ago

Last modified 6 months ago

#5220 new enhancement

Handbook Editor Permissions

Reported by: milana_cap's profile milana_cap Owned by:
Milestone: Priority: normal
Component: Developer Hub Keywords:


DevHub has grown into 8 different handbooks maintained by different teams. User roles caps are not meeting the needs for single Handbook Editor.

For example:

Handbook Editor can create pages in all handbooks but cannot see menus.
Editor can see menus but also can edit all other posts and pages.

Is there possibility to have these caps refined?

Ideally each Handbook would have own editor user role (Theme Handbook Editor, Plugin Handbook Editor etc) and this editor would be able to manage menu for this Handbook.

Current Handbook Editor could become another role, Handbook Author (Theme Handbook Author, Plugin Handbook Author etc). This author could only publish pages in own Handbook and wouldn't be able to manage menus.

If this is not possible then we should at least allow Handbook Editors to manage menus. Handbook Editor is losing usability if user needs to be Editor in order to manage menu for their Handbook.

Change History (2)

This ticket was mentioned in Slack in #docs by estelaris. View the logs.

6 months ago

#2 @milana_cap
6 months ago

Additionally, we would love it if it were possible to assign multiple roles to the same user, E.g., Common APIs Handbook Editor and Explanation Editor. This is a real-life example we had just a couple of days ago.

We have nine different teams managing content at DevHub, and permission to do that should be given by the team responsible AND for the exact content in question. I don't feel comfortable giving all that access to a single person without any human-friendly way to monitor what has changed, when and by whom.

Note: See TracTickets for help on using tickets.