stpaultim
commented
4 years ago A user in the forum is suggesting something that might be related to this (while related, this is probably a different feature):
But it would be useful to have the Favorites article in the Administration menu and the possibility to add any desired administrative page to the Favorites, applied by selecting a check-mark on the administrative page. This saves a lot of time in the daily work of site administration.
In addition, I make such custom items in the Administration menu to facilitate the work of users - without giving access to all items in the Administration menu - which only confuses them and they do not need, I give them only individual tasks that they can do on a comfortable place. Something like User menu, but not in a separate block but in the Administration bar itself.
In short, I suggest that the Administration bar has standard Favorites and User menu items and the ability to easily add and remove selected administrative pages there, through options on the administrative pages themselves.
https://forum.backdropcms.org/forum/feature-ideas-backdrop-cms-118?page=0%2C0#comment-2227
oadaeh
docwilmot
Description of the need
@cellear described a feature idea in the dev meeting today that sounded interesting. He suggested that a site owner should be able to simplify the admin menu WITHOUT having to change roles. New site owners can often be distracted by the many configuration options in the admin menu that do not apply to what they need to be doing. One solution is to login with a less permissive role.
Proposed solution
@cellear suggested adding the ability for a site admin with broad administrative permissions to have the option of turning off the advanced admin features, while maintaining access to the simpler ones. Maybe turn on "simple mode" without having to logout and with the ability to turn on the advanced features at any time.
Alternatives that have been considered
We added the editor role to Backdrop CMS out of the box to address this use case. However, this doesn't fully address the use case outlined here.
This might be a good candidate for a contrib module first?