Feature Request

We would like the ability to customize the error message shown to users when the daily PDF export limit is exceeded. Currently, users see a fixed system message stating that the 500MB daily limit has been exceeded and to try again after 24 hours. While this is informative at a basic level, it does not give us any flexibility to guide users on what they should do next. This has become a growing pain point for us, as customers often get frustrated when they hit this limit and end up raising lots of support tickets for our support team on Zendesk. Since we cannot modify this message, we are unable to: Suggest alternative actions or workarounds Guide users on next steps As a result, we end up handling repeated complaints without being able to proactively manage the user experience at the point of failure. Why this is important If we could customize this message, we would be able to: Provide clear, actionable guidance to users immediately Reduce confusion and frustration Minimize support overhead and escalations with suggested workarounds Maintain better control over how such limitations are communicated Request Allow admins to configure or override the default export limit message, so it can be tailored to the organization’s needs and communication style. This would significantly improve the overall experience and help us manage customer expectations more effectively.

Currently, when exporting an article to PDF from the article settings, table borders are not preserved or displayed in the generated document. Proposed Enhancement: When an article is exported to PDF from the article settings should include visible table borders in the PDF output.

Enable automatic font size adjustment for large tables in PDF exports to ensure better readability without breaking layout. The solution should dynamically scale only oversized tables instead of shrinking the entire content. This would help avoid layout issues while maintaining clarity for complex tables.

When exporting multiple articles as PDF in the site, the PDF export is sent to our email. We would like to have these as a zip file and we would like to download it in the browser level similar to the single behavior export.

Currently, users are unable to export a parent page-type category or the category alone when exporting only a few selected child articles from the knowledge base site. It would be beneficial to support the ability to export selected articles along with their associated page-type categories, as well as the option to export just the page-type category independently. Thank you.

Currently, when exporting an article from the Knowledge Base (KB) site as a PDF, the exported file uses a default title and does not display the article’s last updated date. It would be highly beneficial to provide the following enhancements: Custom PDF Title: Allow users to specify a custom title for the exported PDF instead of using the default article title. Article Updated Date: Include the "Last Updated" date of the article in the exported PDF for better context and version tracking. Summarizing the request -> Title Customization - The readers from the KB site should have the flexibility to add a custom title while exporting the articles to PDF with Custom Font colors -> Article Updated Date: Include the "Last Updated" date of the article in the exported PDF for better context and version tracking. -> Footer Customization: The Footer should contain the name of article-date or version-Language code -> Cover page - The ability to add an end cover page for the PDF's -> Status indicator - The ability to add a status indicator (New, Updated) in the name field.

At present, we do not have control over where page breaks occur for table content when an article is exported in PDF format. The customer is requesting an option to manage this, instead of relying on inserting visible dividers or adding extra spacing within the table to adjust the page breaks.

When exporting a step by step guide article as PDF, instead of displaying the entire image the image is automatically being cropped to where the click was. Our expectation is to see the entire images to be included in the PDF.

When exporting to PDF (we use the default template), there are some basic items that should be included: The bookmarks created have no structure. This is simply a list of the articles. Instead this should replicate the category structure that is visible in the documentation site. The bookmarks are also incomplete in that any headings added to the articles or categories are not included in the bookmarks or table of contents. The structure should include both page names as well as headings. There should be no visible difference between page names and headings in either the table of contents or the bookmarks The table of contents doesn't always have links to the pages as well. There should always be a way to jump from the table of contents to the location further in the document.

Please allow to do PDF exports via an API endpoint, similar to JSON or WebHelp.