-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Cases] RBAC UI Message #95471
Comments
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
The user will see an error toaster when she tries to do an unauthorised action. You mean a message in the UI that will warn the user that she does not have permissions to do certain actions before even acting with the component? |
Yeah you're right about the toaster. No this was just to figure out if a toaster is good enough 🤷♂️ I just wanted to put it on Monina's radar in case she wanted something different that's all. |
Fixed by #101325 |
With the implementation of RBAC within cases we'll need to determine what a good design for communicating to the user when an authorization failure occurs. This will happen if a user does not have the correct privileges to interact with cases. It could be that the user doesn't have any permissions related to the cases feature, or that they only have read permissions, or that the user doesn't have permissions for a specific type of case (meaning they're only allowed to interact with cases created through a single app like the Security Solution, or Observability).
This issue is to track any work needed for communicating these permissions changes around cases to the user.
The text was updated successfully, but these errors were encountered: