Build content in Ponydocs

Acrobat logo Download manual as PDF

Acrobat logo Download topic as PDF

Permissions in Ponydocs

Ponydocs uses a combination of the standard MediaWiki user rights system and version management to support per-product and per-version access to your content.

User access to content and editorial tools

As discussed in the overview of objects in Ponydocs, a given version can be in one of three states: released, unreleased, or preview. The Splunk documentation uses these states in the following way:

  • All Splunk employees are members of an 'employees' group in the MediaWiki user rights system, and can view and edit any product's documentation content in any version state.
  • Docteam members are additionally members of groups granting per-product editorial privileges allowing them to branch and inherit content, as well as create and edit TOC files and manuals.
  • (Non-employee) users can see any content that is tagged with at least one version that is in 'released' state. These users can be logged in to the site or not.
  • Logged-in users can be made members of per-product 'preview' groups, granting them additional permissions to see content tagged with at least one version that is in 'preview' state.

You can create user groups in the MediaWiki user rights system to meet your organization's product- and user-specific requirements, and map them to access to the three version states.

Last modified on 14 July, 2012
Inherit content into a new version

This documentation applies to the following versions of Ponydocs: 1.0

Was this documentation topic helpful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters