[DOCS] Adding better documentation for required RBAC settings for alerting #82375
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bmcconaghy
added
v8.0.0
release_note:skip
gchaps
reviewed
Nov 2, 2020
gmmorris
approved these changes
Nov 5, 2020
bmcconaghy
added a commit
to bmcconaghy/kibana
that referenced
this pull request
Nov 5, 2020
…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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding a more accurate list for which feature privileges are required to gain access to alerting. Also noting that the user requires privileges for actions to hook up actions to alerts.