Keep standard Administration menu

My problem is that I want to use the account menu as custom menu with some added items, which includes the default items like "My account", "My profile" or "Logout". But when I assign the custom menu to the authenticated role, administrators don't have access to the admin menu anymore. Thus, another option would be to add an role exclusion list:

Use the custom menu, if the user has any of the configured roles but none of the exclusion roles, i.e.

Configured roles:
[ ] Anonymous
[x] Authenticated user
[x] Editor
[ ] Site Manager
[ ] Administrator

Exclusion roles:
[ ] Anonymous
[ ] Authenticated user
[ ] Editor
[x] Site Manager
[x] Administrator

So, every authenticated user (and editors in special) get the custom menu, except they are admins or site managers.

I will look into this as soon as i have some time

Pushed to 1.0.x, can you please test it?

1.0.6 release

Awesome, thanks. Both variants (adding custom menu items to admin menu, excluding roles) work.

I just wanted to check here if I understand correctly before creating a separate issue:

Looking at Gin's code, a lot of the menu is hardcoded without access checks in getNavigationStructure.

Using this module, we can indeed add or replace items in the "middle" part (which is awesome by the way), but the top and bottom part are always displayed.

In my usecase, I have a role which can only view some custom entities, but the "Create" menu -> top will always be shown for all content types resulting in access denieds.

Now, I can fix this in custom code, but I'm wondering whether this should be an (access) issue in the gin project, or additional toggles in this module?

I dont really touch that part of the toolbar, so i would say its a gin access check issue.