Feature Request

This request was created on behalf of Emily We would like to enable search specifically within a glossary, rather than across the main knowledge base. The intent is to use the glossary as a wiki-style repository focused exclusively on definitions. Additionally, we would like the glossary entries to have their own dedicated tags or categories, separate from the main knowledge base. These tags/categories would help classify definitions based on teams, products, or domains. Examples: Team-based: Communications Product-based: iPhone X This would allow users to quickly find and filter definitions relevant to a particular team or product without navigating through standard articles. Thank you.

Customers working with a large number of snippets (such as FAQ accordion blocks) need a way to quickly reuse an existing snippet structure. Currently, Snippets do not support duplication or template creation, requiring users to manually copy and paste HTML each time they create a new snippet. Requested Enhancement: Add an option to duplicate an existing snippet or save a snippet as a template that can be selected when creating new snippets. This will significantly improve efficiency and reduce manual effort for customers managing high volumes of reusable content.

We would like the ability to delete the default template associated with the English (EN) language in our portal. The default templates for English (EN) exist by default in the portal. It cannot be deleted or removed using the current UI Even if the templates are not removable, we would like the default templates not to appear while creating a new article.

In content reuse categories, I have to click or edit a list entry to see its content. I would like to see a preview already when I hover the mouse over the list entry, similar to how previews are shown in the editor.

It would be extremely useful if the AI automatically applied glossary terms during translation. This would ensure brand consistency and accurate terminology across all languages, without requiring manual correction after each translation. Ideally, the system should detect and replace relevant terms directly from the glossary, so the translated text always aligns with approved brand vocabulary.

Currently, when entering a term in the glossary, the latest term shows at the top of the list when using the " / " key to insert a glossary term. While helpful, would you consider changing, or having the option to change to, alphabetical? This would also be helpful in the glossary page itself so the term can be found more easily.

The customer is looking for a feature that allows creating a parent document that combines content from other articles—either entire documents or specific parts—and ensures any updates to the original content are automatically reflected in the parent document. This is especially important for generating documents like legal exports, where accuracy and consistency are critical. Current Workarounds Explored: Tags (not suitable for embedding content) Variables, Snippets, Glossary terms (helpful but limited) iFrame (not suitable for export) Replicate Article (cannot combine multiple sources or partial content) Looking for a structured way to reuse article blocks or tagged sections within another document, with export and sync support.

We do not have the option to select the font size of 16px in the variable creation section. Since we are using the same size(16px) in all their articles. In the content reuse section, we don't have the exact list of sizes which is available in our editor. It would be great if we could include all the font sizes in the content reuse editor as well.

We are currently unable to save or update a snippet while in code view. We need to exit the code view first to save the content. It would be helpful if the update button could be greyed out while editing in code view.

Currently, the exact term used within the glossary is shown on the page. This doesn't look that great when different capitalization, plurals, or tenses are used in the text that the glossary term is used within. A simple example would be to have a glossary entry called "Canada Goose" which might get used in different scenarios. In many places, the term should not be capitalized for the word "Goose". In places where they are talking about a flock of "Canada geese" this would also need to be altered. Having a replacement text available as the glossary is used would be desirable.