github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 09:19:04 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS] Adding better documentation for required RBAC settings for alerting (#82375) (#82740)

Browse source 
* Adding better documentation for required RBAC settings for alerting

* Bolding feature name and spelling out ampersand

* clarifying explanation of action privileges needed
This commit is contained in:
Bill McConaghy 2020-11-05 11:39:43 -05:00 • committed by GitHub
parent 3d3d3bc944
commit b2ef36423c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/user/alerting/alerting-getting-started.asciidoc
View file

@ -169,12 +169,15 @@ If you are using an *on-premises* Elastic Stack deployment with <<using-kibana-w
To access alerting in a space, a user must have access to one of the following features:
* Alerting
* <<xpack-apm,*APM*>>
* <<logs-app,*Logs*>>
* <<metrics-app,*Metrics*>>
* <<xpack-siem,*Security*>>
* <<uptime-app,*Uptime*>>
See <<kibana-feature-privileges, feature privileges>> for more information on configuring roles that provide access to these features.
See <<kibana-feature-privileges, feature privileges>> for more information on configuring roles that provide access to these features.
Also note that a user will need +read+ privileges for the *Actions and Connectors* feature to attach actions to an alert or to edit an alert that has an action attached to it.
[float]
[[alerting-spaces]]