[DOCS] Creates field and document level security overview #55
Conversation
This file contains hidden or 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
lcawl force-pushed the lcawley-field-level-security branch from 42d9cb4 to 92f7eba Compare 
jaymode approved these changes Jun 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
This PR splits off separate overview pages for field-level security and document-level security and moves them higher in the table of contents.
It also adds code snippet testing for the examples.
This content had previously been rather buried in this long page:
https://www.elastic.co/guide/en/elastic-stack-overview/master/field-and-document-access-control.html#field-level-security
https://www.elastic.co/guide/en/elastic-stack-overview/master/field-and-document-access-control.html#document-level-security