Update configuring-reporting.asciidoc #173309
Open
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
A customer opened a case about the steps listed in https://www.elastic.co/guide/en/kibana/8.11/secure-reporting.html#grant-user-access Per the customer, and I tend to agree, the existing wording is accurate but hard to follow, especially for a non-native english speaker. In particular, this bit: """ Enable application privileges in Reporting. To enable, turn off the default user access control features in kibana.yml: """ It's technically accurate, but to dissect the "To enable, turn off..." part you have to do some further reading. I was hoping that maybe there's a way to just rephrase this part or slightly restructure it to make it clear that: In order to enable application privilege reporting...you must disable the other setting first, otherwise you can't see it. That's my pre-coffee, non-technical-write version. Please feel free to modify this further if my change is lacking.
|
Documentation preview: |
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.
A customer opened a case about the steps listed in https://www.elastic.co/guide/en/kibana/8.11/secure-reporting.html#grant-user-access
Per the customer, and I tend to agree, the existing wording is accurate but hard to follow, especially for a non-native english speaker.
In particular, this bit:
It's technically accurate, but to dissect the "To enable, turn off..." part you have to do some further reading. I was hoping that maybe there's a way to just rephrase this part or slightly restructure it to make it clear that:
In order to enable application privilege reporting...you must disable the other setting first, otherwise you can't see it. That's my pre-coffee, non-technical-writer version.
Please feel free to modify this further if my change is lacking. I think you would want to backport this to all other versions of the page.
Summary
Summarize your PR. If it involves visual changes include a screenshot or gif.
Checklist
Delete any items that are not applicable to this PR.
\
For maintainers