Show inaccessible features as disabled rather than hidden, or update docs
I just spent several hours trying to understand the documentation for setting up CI. It made no sense to me. Throughout the docs they would refer to UI and features that were missing for me. I searched Google, etc and couldn't figure out what was going on.
Finally I got the idea that maybe it was related to permissions. Sure enough, after looking into Gitlab permissions, I learned that I'm not seeing the functionality because I am a Developer, not a Maintainer.
There are two ways to fix this. The first, probably easier one on your end, is to ensure that the documentation explicitly says that a feature or UI is only available for users with specific permissions. The second, probably better, is to simply show all functionality, gray out the items that I don't have permission to use, and then provide a tooltip that says I don't have permission to do that.
Steps to reproduce
Follow the documentation for CI environment variables set up, but with Developer access. The docs don't make sense.
What is the current bug behavior?
Documentation directs me to UI that isn't visible because I am a developer.
What is the expected correct behavior?
Documentation that explicitly says I need Maintainer or Owner permission, everywhere items are mentioned. (i.e. don't just mention this on an overview page because we won't see it.
OR, show grayed out UI elements that are mentioned in the docs, rather than hiding them completely.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Results of GitLab application Check