Feature Request

We are using custom HTML in our Markdown articles and applying site-level CSS through to style the content and render flowcharts on our knowledge base site. The flowcharts display correctly on the published site, but when we export the same articles using the PDF export option, the content appears without the applied CSS styling. As a result, the flowcharts lose their intended layout, colors, borders, and visual structure in the exported PDF. We understand that site-level Custom CSS currently applies only to the knowledge base site and is not supported in PDF exports. However, this limitation prevents us from maintaining a consistent presentation across the online documentation and downloaded PDFs. We would like the PDF export functionality to support site-level Custom CSS so that custom HTML elements, flowcharts, diagrams, and other styled content retain the same intended appearance in exported PDFs as they do on the published knowledge base site. Could you consider adding support for site-level Custom CSS in PDF exports, or providing an alternative way to define custom styles specifically for PDF generation? This would help us maintain consistent formatting and presentation across both the published knowledge base and its downloadable PDF documents.

We use two Google fonts in our knowledgebase, but we can only use the standard Document360 fonts in PDF exports. So, we cannot make PDF exports match the style of the knowledgebase. Please make it possible to use Google fonts in PDF exports.

The Title and Description fields on PDF template cover pages and end pages accept only plain text, with no support for bold text, multiple paragraphs, or page breaks. Extend the cover page and end page Title and Description fields to support basic rich-text formatting and the ability to insert page breaks. Benefit: Users could design multi-section or visually structured cover and end pages directly in the template editor, without substituting an uploaded image for what would otherwise be simple formatted text.

PDF template design fields such as the cover page, end page, and footer currently accept only a fixed set of built-in placeholder metadata (for example, PDF Generated Date or Article Title). Users cannot insert their own Variables or Snippets into these fields. Allow custom Variables and Snippets to be inserted into PDF template text fields (cover page, end page, and footer), alongside the existing built-in placeholder options. Benefit: Teams could reuse their own centrally managed product names, version numbers, disclaimers, and other standardized content directly in PDF cover pages and footers, keeping exported documents consistent with the rest of their knowledge base.

Right now, you have to check the export screen to see whether you've reached your limit or if a customer complains they can't export. There should be an early alert at 80%, 90%, 95%, etc.

Teams can only see their remaining monthly PDF export credit balance by manually opening the Export articles page and checking the live usage widget. There is no way to be notified automatically as the balance runs low. Add configurable threshold-based alerts (for example, delivered by email, webhook, Microsoft Teams, or Slack) that trigger when the PDF export credit balance drops to set percentages, such as 20 percent and 10 percent remaining, and when the balance is fully exhausted. Benefit: Teams get advance warning before exports are blocked, letting them plan large export batches, reallocate usage, or request more credits ahead of time instead of discovering the limit has already been reached.

The KB site enforces a 500 MB daily limit for PDF downloads, but there is no visibility on the Admin side to track how much of this limit has been consumed or how much remains. The warning appears only after the limit is exceeded, which prevents proactive monitoring and planning. There are currently no audit logs available for PDF exports from the KB site. Admins cannot see who initiated downloads, how much data was exported, or when the activity occurred. Audit logging should be added for transparency and tracking. In addition, a per export size limit should be introduced. This will ensure that one large export does not exhaust the daily quota and impact other customers sharing the same environment.

A selection of PDF in the device type for conditional content would be great. We often have videos and graphics in the articles. If we need to create a pdf for a customer, we can't filter out that content. In PDF, videos in particular make no sense.

HTML editor for PDF templates: This would let us customize the layout and styling the way we need it. Workspace-specific default templates: The generic template doesn't reflect our product, and that shows in the exported PDFs. We'd like each workspace to have its own branded template. Custom variables (placeholders): We can dynamically insert product names, guide titles, dates, and other metadata into the template. The current placeholders don't give us what we need Rich text/formatting on the "End Page": Currently there's no way to style the content Increase the "End Page" description character limit from 500 to 1000+. We need more room for context. Thank you.