kibana/packages/kbn-alerts/README.md at 51f8feaea06f2c93d2a97ed0aa944bf918180f06 - maxmustermann/kibana - tilera Git

maxmustermann/kibana

Yara Tercero 9fa41d1aef

[Security Solution] - Updating UI to work with new kibana privileges abstraction on alerts (#108961 )

## Summary

Holy moly. 

What is happening in this PR? 🤷🏽‍♀️ Let's break it down:
- Added a package `@kbn/alerts` - another one?! ...yes
  - This is meant to add shared hooks and components around alerts as data
  - `useGetUserAlertsPermissions` - accepts the Kibana capabilities object and returns whether the user has `read` and `crud` alerts privileges
  - `AlertsFeatureNoPermissions` - component displayed when user does not have alerts privileges
- UI changes for user with NO alerts privileges
  - `Alerts` tab hidden in security solution side navigation
  - `Alerts` tab hidden in rule details page  
- UI changes for user with alerts READ ONLY privileges
  - alerts checkboxes hidden in alerts table
  - alerts bulk actions hidden in alerts table

2021-08-18 14:48:31 -04:00

7 lines

297 B

Markdown

Raw Blame History

 # AlertsFeatureNoPermissions
 Component displayed when a user with alerts permissions of `none` attempts to access alerts page.
 ## useGetUserAlertsPermissions
 This hook parses through the uiCapabilities Kibana object to determine if the user has Kibana `read` or `crud` permissions for alerts.