Feature Request

Currently, the Pre-publish check displays a warning if a broken link is detected (though it is often wrong), but does not display what link it is detecting as broken. This makes the warning a liability and a time-sink, as you have to check every link on the page to verify that they are still working and often discover that there is no issue with any link on the page. The Pre-publish check should list the link that it is referencing as "broken" and give us the option to ignore the warning so it does not appear again.

When an article has no article-level review reminder override configured, its Review reminder panel does not indicate that a project-level Auto-schedule review reminder is currently governing when the article will go stale, nor what interval applies. Display, within the article’s own Review reminder settings panel, the effective reminder interval and whether it is coming from the project-level default or an article-level override. Benefit: Contributors can immediately see, from inside the article editor, why and when an article will become stale, speeding up triage of stale-article notifications without cross-checking project settings separately.

Absolutely LOVE the new archive function! I was wondering if the "Archived From" category on the Archived Page could be wrapped so we can see the entirety of the breadcrumb? Or if you hover over it, the full breadcrumb will show? We have some long ones at times, and it would be helpful to see. thank you.

Teams managing large content audits or ongoing maintenance need to identify an article's internal category/type at a glance while browsing the Categories & Articles tree in the portal — without opening each article or applying a filter every time. Labels serve this purpose today, but they only surface when you filter or open the All Articles list — they aren't visible inline next to the article title in the tree. Category emoji icons are visible in the tree, but they're public-facing, so they don't work for internal-only classification, and emoji only apply to categories, not individual articles. Workflow statuses were also considered, but those are tied to the publish pipeline (an article resets to the system "Published" status once live), so they can't hold a persistent internal tag. Request: Add an option for Labels (or a new internal tagging feature) to display as a small colored indicator/chip directly next to the article title in the Categories & Articles pane — visible only in the portal, never on the public site, and never included in PDF/Word exports. Ideally, colors could be assigned per label so different content types are distinguishable at a glance across hundreds of articles, without needing to filter or open each one. Why it matters: For any team doing large-scale content audits, migrations, or ongoing maintenance, being able to visually scan the tree and instantly recognize article types/status (internally) would save significant time versus repeatedly filtering through the All Articles list.

It would be nice to be able to assign content to an owner and then have that person only receive notifications for any feedback submitted. I was advised that currently all admins receive notification and then it must be manually assigned.

The file folder is helpful in which to store docs to link, but it appears the system does not offer version control. The system does allow replacing the doc, but the prior doc is not viewable. For continuity, the system should provide, store and be able to view prior documents for auditing purposes; now we have to utilize an external system to store information within those files for documentation purposes.

Can we please be able to link to content other than headings - say create bookmarks, and link from elsewhere to these bookmarks?

A consolidated view of all conditional content blocks applied across different articles would be highly beneficial for more effective management.

Currently, glossary entries with the same Name and Term cannot be imported across different languages, as the glossary Name must be unique across the project. The customer uses an external translation service and imports glossary entries separately for each language. In some cases, the Term remains the same across languages (for example, "Widget"), while only the definition changes. The customer would like the ability to import the same glossary Name and Term across different languages and have them treated as language-specific entries. The glossary import should also provide an option to specify the target language and name of the glossary in the csv.

This request was created on behalf of Marni It would be better if we have an option to create snippet inside a snippet. Thanks.