Disable navigation theme selection on user level
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Disable end-users to change (navigation) themes
Target audience
(Large) Companies with a reasonable amount of end-users running multiple instances of GitLab or IT administrators who want to enforce company branding
Further details
Use case: Company running a test and production GitLab instance. The administrator wants to have the navigation theme for production set to eg blue and for development to red. In this way if users report an issue with screenshot he knows immediately on sight to which instance a user is referring to. If an end-user may change this he needs to find out first to which instance he's referring too.
Use case: Strict company branding is active in a company so it must be prevented that end-users "break" this policy
Advantage: stricter application setup which allows to give better and faster support and avoids a mix of user interface themes used by users.
Proposal
Add an option in the admin area to set default themes (preferably in the Appearance section). When this is activated the customization should be disabled. Eventually let the option to change it but then you need an additional checkbox in the Admin area setup "Disable (navigation) theme change"
What does success look like, and how can we measure that?
Success metric is that a consistent UI in terms of colors/themes can be enforced thus resulting in easier/faster support Acceptance criteria is that you enforce the option that the theme can't be changed and you go to the user settings and verify that you can't change it anymore (hidden or disabled)