Skip to content

Commit

Permalink
[DOCS] Adding better documentation for required RBAC settings for ale…
Browse files Browse the repository at this point in the history
…rting (elastic#82375)

* Adding better documentation for required RBAC settings for alerting

* Bolding feature name and spelling out ampersand

* clarifying explanation of action privileges needed
  • Loading branch information
bmcconaghy committed Nov 5, 2020
1 parent 1796b5e commit 4320cb5
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion docs/user/alerting/alerting-getting-started.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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]]
Expand Down

0 comments on commit 4320cb5

Please sign in to comment.