You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
All menu items should have a way to be hidden or disabled, given the rapid expansion of features.
Menu items still show for things that are unused by certain roles or cant work because underlying permissions the plugin requires are denied, leading to many of the features looking "broken" when they are just disabled.
This behaviour already exists for the Security plugin, where "Security" menu only shows when "security_manager" role is assigned.
Describe the solution you'd like
Have each menu item map to a role, like the "security_manager" role.
Introduce inheritance/composition for roles/permissions, so meta roles can be created that reference other roles, effectively giving the administrator the ability to centralize without having to manage "Mapped users" for every granular role.
A nice to have alongside this would be a way to see what each plugin requires for permissions to enable each of it's features, so enabling a particular menu item won't be crippled from the start, like "Reporting" where write access is required but not explained:Reporting Documentation
Related component
Plugins
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
All menu items should have a way to be hidden or disabled, given the rapid expansion of features.
Menu items still show for things that are unused by certain roles or cant work because underlying permissions the plugin requires are denied, leading to many of the features looking "broken" when they are just disabled.
This behaviour already exists for the Security plugin, where "Security" menu only shows when "security_manager" role is assigned.
Describe the solution you'd like
Have each menu item map to a role, like the "security_manager" role.
Introduce inheritance/composition for roles/permissions, so meta roles can be created that reference other roles, effectively giving the administrator the ability to centralize without having to manage "Mapped users" for every granular role.
A nice to have alongside this would be a way to see what each plugin requires for permissions to enable each of it's features, so enabling a particular menu item won't be crippled from the start, like "Reporting" where write access is required but not explained:Reporting Documentation
Related component
Plugins
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: