Add UI hiding features for role requests, expiring roles, and ownership selection #278
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!,
We don't use Role Requests at all, and our group ownership is handled through YAML configs that sync with the DB via plugins. The manual UI controls for these features are creating user support noise - people see buttons they shouldn't use and ask us about them/click them & generate unneeded notification pings/support tickets.
This PR adds config flags to hide UI elements that organizations might not need:
Everything defaults to current behavior (no breaking changes). Just gives orgs a way to streamline the interface to match their actual workflows.
This would let organizations hide the parts they don't use and reduce user confusion.
All the backend functionality stays intact - this is purely frontend conditional rendering based on config flags. Added docs and examples following the existing config pattern.
This is me trying not to have to manage a fork again, but I realize some of this might be weird for upstream.
Let me know what you think.
-Jonathan