Feature Request

If I have the KB automatically set an article status to New when it's published or updated, I should be able to manually override that setting on a per-article basis. Currently I can't do that, which is annoying.

Allow all links in the Knowledgebase to be in a new tab, or specifically all extrenal links

Requesting support for industry-standard sitemap index files (sitemapindex.xml) as external sources in AI Assistive Search. Currently, sitemap index files are rejected, requiring customers to either consolidate all URLs into a single <urlset> sitemap. Supporting sitemap index files would allow customers to leverage their existing SEO infrastructure and simplify AI search source configuration.

Problem Statement: Managing multiple workspaces with similar configurations requires repetitive manual work for each workspace, increasing errors and inconsistencies. Suggested Enhancement: Introduce a Settings Template feature that allows users to save a workspace's settings as a reusable template and apply it to new or existing workspaces, with an option to override specific settings per workspace. Customer Benefit: Users reduce repetitive configuration work, maintain consistency across similar workspaces, and onboard new workspaces faster with pre-configured settings.

Problem Statement: Project-level settings affect all workspaces instantly with no warning. Users may inadvertently apply changes intended only for a specific workspace or situation. Suggested Enhancement: Display a confirmation dialog when a user attempts to save changes to a project-level setting, stating: "This is a PROJECT-LEVEL setting. Your changes will apply to ALL workspaces in this project. Continue?" Customer Benefit: Users have a safety checkpoint to prevent accidental project-wide setting changes, reducing configuration errors and their downstream impact.

Problem Statement: Users managing multiple workspaces have no way to view or compare settings across workspaces. This makes it difficult to understand configuration state or identify inconsistencies. Suggested Enhancement: Create a Settings Audit or Comparison view that allows users to select multiple workspaces and see a table or matrix showing workspace-level setting values across those workspaces. Highlight differences or inconsistencies. Customer Benefit: Users gain visibility into configuration state across workspaces, can identify drift or inconsistencies, and make informed decisions about settings updates.

Problem Statement: Users cannot quickly and visually determine whether a setting applies project-wide or to the selected workspace only. The current UI requires users to look for the presence/absence of a workspace dropdown, which is unintuitive and error-prone. Suggested Enhancement: Add prominent scope badges (e.g., "PROJECT-LEVEL" or "WORKSPACE-SPECIFIC") next to each setting name. Use visual styling (color, icon, or banner) to make scope immediately obvious. Customer Benefit: Users instantly identify the scope of any setting before making changes, reducing accidental project-wide modifications and improving confidence in settings management.

Provide a dedicated dashboard that displays current usage and limits for categories, articles, and other key resources, such as AI features within the project. This would give administrators clear visibility into resource consumption, help identify when limits are being approached, and eliminate the need to manually track or request this information from support.

For privacy and GDPR (data collection) reasons, our legal dept. would like us to be able to add our own disclaimer text when a user click the follow button for an article. That is, to be able to edit the text where the person adds their email

In the Settings/Team Auditing section, the logged items do not show any detail of what changes were made. For example, it says "Project Updated" but does not indicate what was changed. It would be much more useful if we could see exactly what changes were made and when.