This document will show you how to create a document that is restricted to a subset of your internal users. We will then show you how to embed the document with restricted content into a "container" document which is intended for general consumption.
In some cases, you may want to publish a general document, but would like portions of the content viewable only by a subset of your users. While this is not possible within a single document, you can accomplish this by creating a completely separate document with the restricted content and feeding that into the document for general consumption (e.g. the container document in which you will embed your restricted content via the IncludeDoc feature).
If you have not done so yet, create a User Access Group where the members are the users who should be able to view the restricted content. See KB User's Guide - Users Tab - User Access Groups and Limited Access Groups for a refresher on creating and managing User Access Groups.
Create a document with all the restricted content you wish to share with a select number of people, i.e. the members of the User Access Group you created. We recommend these document settings:
After activating the document with the restricted content, keep the document ID number handy as you will be needing it shortly.
Next, begin creating the container document for general consumption based on your KB group's workflow.
On the document edit screen of the container document, determine where you feel the restricted content would fit best. Type the document ID number of the restricted document in the body of the container document, highlight that number and click on the IncludeDoc button.
WYSIWYG Design Editor:HTML Editor:
IncludeDoc content that has been restricted by UserGroup Access is not viewable by those outside of the UserAccess group, even if looking at document view source or inspect element. Nor will IncludeDoc tags be visible.
In the image below, there is zero indication of an embedded document with restricted content that has been placed ABOVE the "Make it a great fishing season by" section of the document.
The "Includedoc Chain" can go up to five layers deep (so there is no infinite looping). When the depth limit is reached, the last layer of 'IncludeDoc'(s) is converted into 'LinkDoc'(s). Access permissions, 'LinkDoc' tags, 'Htmlentity' tags, etc. are all honored along the "IncludeDoc chain". Infinite loops are prevented without enforcing any depth limit.