Support "All" or "None" feature privileges #106589
Labels
enhancement
New value added to drive a business result
Feature:Security/Feature Controls
Platform Security - Spaces & Role Mgmt feature controls
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
loe:small
Small Level of Effort
Team:Security
Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Describe the feature:
Currently. feature privileges must be "All", "Read", or "None" (not counting sub-feature privileges).
However, for some features it may only make sense to provide "All" or "None".
Describe a specific use case for the feature:
One example of this is Dev Tools; there is no practical difference between "All" and "Read".
Another example is the ability to log into Kibana without granting access to any particular feature: #102129
Another example is the ability to access Space Management: #51759
Another example (a bit of a stretch) is if we ever decide to promote an
independent
sub-feature privilege to a top-level feature privilege; these are currently represented with a checkbox, which is essentially already "All" or "None".The text was updated successfully, but these errors were encountered: