Feature Request

Currently, a Document360 project supports a single base domain, which is shared across all workspaces within that project. If a customer wants each workspace to be hosted on a completely different domain (not just a different subfolder or path on the same domain), this is not natively supported. The only current workaround is to purchase separate projects, one per required domain. We would like to request the ability to assign a distinct custom base domain to each workspace within the same project. This would allow teams managing multiple workspaces for different products, following different branding, under the same company, to maintain a single project (with shared settings, categories, and management) while still publishing each workspace under its own unique domain. Use case: Our organization has multiple workspaces under one project, each representing a different product with its own branding, under the same company. The target audience for these products may be the same in some cases and different in others. When the target audience is the same, we prefer to keep these as workspaces within one project rather than move to separate projects, so that we can view analytics for that audience in one place instead of across separate dashboards. Staying within a single project also makes it easy to replicate content across workspaces. The request is simply to allow a different base domain for each workspace, without needing to maintain separate projects (and separate subscriptions) just to achieve domain separation. Requested capability: Ability to configure a unique custom base domain per workspace within a single project. Independent SSL/DNS configuration per workspace domain. Retain shared project-level features (content replication across workspaces, analytics, user management, categories) even with different domains per workspace. This would reduce the need to purchase multiple projects solely to achieve domain-level separation between workspaces.

When replicating articles from one workspace to another, hyperlinks within the replicated content continue to point to the original workspace instead of updating to the corresponding articles in the destination workspace. This is a significant issue for organizations that maintain multiple workspaces for different customer bases. Readers who only have access to the destination workspace (workspace 2) cannot access the linked content because the hyperlinks redirect them to the source workspace (workspace 1), which they do not have access to — even when the linked articles have already been replicated to workspace 2. Example: Article A is replicated from workspace 1 to workspace 2 Article A contains hyperlinks pointing to Article B in workspace 1 Article B has also been replicated to workspace 2 However, the hyperlinks in the replicated Article A still point to Article B in workspace 1 Readers in workspace 2 cannot access workspace 1, so the links break for them Expected behavior: When an article is replicated to a destination workspace, any hyperlinks pointing to articles that also exist in the destination workspace should automatically update to point to the correct articles within that workspace. Impact: This is causing a poor reader experience for customers who are scoped to a specific workspace and do not have access to the source workspace.

We need a way to get Eddy AI search questions, conversations, and feedback data without manually clicking Export CSV every time. Right now there's no API for this data. The only workaround is scripting the internal export button, but that's not supported, needs a stored login, gets blocked by Cloudflare bot protection, and only gives short-lived tokens with no way to refresh them. We'd like an API endpoint to pull this data using a normal API token, so we can access it on a schedule without any of the above issues. Here's the linked FR : https://feedback.document360.com/feature-request/p/external-access-to-eddy-ai-search-queries Thanks

Currently, headings located inside Tabs cannot be linked using anchor links. It would be helpful to support linking directly to headings within Tabs, enabling users to navigate to specific sections inside tabbed content.

When a user submits feedback, they must select the ‘Keep me updated’ checkbox to receive updates about their feedback. This checkbox is currently cleared by default. If the user does not select it, they will not receive any updates. Would it be possible to have this checkbox selected by default? Users would then automatically receive updates about their feedback unless they clear the checkbox to indicate that they do not wish to be kept informed.

When a glossary term is deleted, the system currently removes both the glossary reference and the associated text from article content. This behavior makes it difficult to reuse or retain the original wording within articles. We request an option to preserve the term text by converting it into plain text instead of removing it entirely. Problem Statement In the current implementation, deleting a glossary term results in the complete removal of that term from all associated articles, including the visible text. This creates several issues: -> Loss of content within articles -> Difficulty in identifying where terms were previously used -> Manual effort required to reinsert or replace removed text Expectation When a glossary term is deleted, users can choose between: -> Remove completely -> Convert to plain text

It's only possible to have 500 terms at the glossary. I've tried to import more and it retrieves an error toast (with missing written content, it shows the code error, not a user friendly one). In the documentation there is no information about this limit. It's important to have more than 500 terms specially when we have multi language and several workspaces (in my case we have 12 workspaces available in 3 different languages).

One of our customers would like a custom login page so that instead of the generic login page, the users to be redirected to their custom SSO login page (similar to the initial login experience), allowing users to simply click the SSO button and sign back in without having to enter their email/domain again.

A paid POC customer has requested a visual notification indicator for the "What's New" (megaphone) icon on the KB Site. Problem: Currently, readers need to click the What's New icon to check whether any new or updated articles are available. Unlike the Read Receipt bell icon, which displays a red badge indicating pending acknowledgements, the What's New icon provides no visual cue that fresh content is available. Requested Enhancement: Display a notification dot or badge on the What's New (megaphone) icon whenever one or more articles have been published or updated within the configured "Show article status for [X] Days" window. The indicator should: Appear when new or updated content exists within the configured time window. Follow the same visual pattern as the existing Read Receipt notification badge for consistency. Automatically clear once the reader visits the What's New page (or alternatively, when the icon is clicked). Work for both Public and Private KB Site 2.0 projects. Customer Value: This allows readers to know at a glance when new content is available, improving discoverability and engagement with recently published or updated articles while maintaining a consistent user experience with the existing notification patterns.

Provide a mechanism for external stakeholders to access Eddy AI search analytics and user feedback without requiring access to the Document360 Feedback Manager. The customer is requesting publicly accessible API endpoints or a notification mechanism that enables external stakeholders to retrieve Eddy AI search queries and feedback.