Documentation Visibility Content Overview
The three "how-to" documents below describe how to use licenses to control the visibility of documentation files and content. You can learn how to set up a simple scenario where you have a set of documents for an API with an overview doc, and one document for each API operation. The documentation for some of the API operations should only be visible to users with an admin license, while the rest should be visible to all users. All of the docs also contain a content element for example, a footer) with links to each of the other docs.
The additional documents provide reference information about managing document visibility, and a use case with instructions and video.
How to Manage API Visibility with Licenses
A how-to guide for creating a simple setup to use licenses to control the visibility of APIs.
How to Control Document File Visibility in the Default Theme
A how-to guide for using licenses to control the visibility of documentation files in the Community Manager developer portal.
How to Control Document Content Visibility
A how-to guide for using licenses to control the visibility of content elements in documentation files.
API Documentation Tagging
Learn how to tag your API documentation to control visibility of documentation files.
Use Case: Controlling API Documentation Visibility with Licenses
Step by step instructions, and illustrations, for setting up an API and using the Licenses feature to add privacy on certain operations so that different users have visibility of different operations, depending on the user's license.
