Skip to content

Per-reader filtering in PDFs

A publication is filtered with exactly the same rules as the site. Chapter conditions cover everything in the chapter.

  • Conditions on a chapter, part or topicref apply to everything under it. The Administrator Guide's self-hosting chapter has product="core", so a managed customer's copy has no such chapter at all.
  • Conditions on topics and elements apply as on the site, paragraph by paragraph.
  • A heading whose chapters are all hidden is left out, and so is its contents entry.
  • A reader who can see nothing in a publication gets a 404, the same as for a publication that does not exist, and no download link.
  • Links to topics in the same publication jump within the PDF. Links to other topics point at the docs site when the reader can see them there, and are plain text otherwise.
  • Only images in topics the reader can see are embedded.

Who shares a render

On the hosted site a PDF is printed once per release and entitlement set, then cached in the blob store, so readers with the same products, features and version share one file. A new release gets new files; nothing needs clearing. Because one file serves several organizations, the hosted cover never names an organization.

In the previewer, the cover says "Prepared for" the preview reader's org, when the reader has one, so you can tell printouts apart. The staff view prints the first alternative of each conditional key.