Feature Request

We need the ability to link words or phrases within inline code blocks to other articles. Currently, the Doc360 editor supports inline linking, but the link doesn't render in the editor or on the published site, making it invisible to users (images 1, 2, and 3). This native support is critical for our documentation, as we frequently use inline code for visual formatting of important terms and require those terms to be linked to topics that explain at length about them.

Team, we have tested the KB widget implementation in our environment (bottom right), and we saw clicking the widget only opens the article that was configured in the settings without displaying any Related Articles underneath (image 1). Internally, we've decided to show no more than one article so we're not interested in "Show list of articles" option under "Update URL mapping" (image 2). Now, we're aware, Related Articles show on the published KB site at the bottom (Image 3), but the same isn't visible in the KB widget. Since the native functionality already exists, we want you to mimic this in the widget area - the white space below the configured mapping (image 4).

Step-by-Step Guide: Requested Enhancements: • Optional Image Inclusion: Allow users to choose whether to include screenshots in step-by-step recordings. Use case: We usually do not include images in step instructions to save editing and maintenance time, reduce scrolling, and improve loading performance - especially since our cloud-based applications already display the necessary screens online. • Embed Recordings Within Other Normal Article: Enable adding a recorded guide/recorded steps inside an existing article (for example, within a “Steps” section of a task topic). Use case: Currently, a recorded step by step guide does not allow for an introduction section. Also, it’s not possible to add callouts in the introduction section nor below the steps. Our standard task topic structure includes an introduction section followed by a “Steps” section. Both in the introduction section and below the steps, notes (callouts) can be added. We need to position the recorded steps inside a task topic to integrate seamlessly into this topic structure. Additional Requirements: • Numbered List Formatting: Recorded steps should be insertable as standard numbered lists. Use case: This aligns with our current formatting style and allows sub-steps or sub-tasks to be easily added. • Add Notes to Recorded Steps: Include the ability to attach notes (callouts) to individual steps. Use case: Notes are often necessary for context or clarification, which the current step editor does not support.

Eddy AI: Requested Enhancements: • Support for Markdown Files in “Write Article”: Allow creation of articles from markdown files. Use case: Our development teams document in markdown; easy upload into Eddy AI would streamline content creation. Additional Request: • Extend ‘Create from File’ to Other AI Functions: Make the “Create from file” capability available for “Continue Writing” and “Rewrite this Article”. Use case: We often revise existing content based on new features, and leveraging relevant markdown documentation as AI input would be highly beneficial.

Currently, Document360 offers Public (viewable by anyone) and Private (restricted to specific users/groups) article visibility. There is no middle-ground option that allows a user to see the entire site's structure while still requiring authorization to read the content. Proposed Solution: Add a new accessibility level called "Protected Mode" or "Protected View." In this mode, users can see all article titles in the table of contents, including both public and private ones. However, when they click on any article, they are prompted to log in (if not already) and must have explicit viewing permissions to read the content. This provides transparency into the full knowledge base structure for authorized stakeholders (like certain customer tiers or partners) without granting immediate access to sensitive private content, improving navigation and manageability.

Currently, managing self-registered readers and their group assignments cannot be done programmatically through the Customer API. This forces manual administration in the portal, which is inefficient and error-prone for organizations with a large number of users. Proposed Solution: Extend the Customer API to include endpoints for: Managing self-registration settings (enable/disable, allowed domains). Automatically assigning readers to specific groups upon registration via API configuration. Programmatically listing, adding, and removing readers from reader groups. This enables seamless user lifecycle management, allows for integration with external identity systems, and significantly reduces the manual overhead of maintaining readers and their permissions at scale.

Many of our users need to see a big picture. This is made possible using workflows that are built on tools like draw.io . Here's an example - https://support.whatfix.com/docs/understandingthewhatfixworkflow . It would be great to be able to create these from inside Document360 - using Draw.io .

One of our customers has provided the below feedback: In the Advanced WYSIWYG Editor, Code View is cluttered with excessive markup, making it difficult to read and visually scan content. Customer has requested a cleaner, more minimal markup view to improve readability and overall editing efficiency.

We want to be able to add comments to text inside snippets just like with normal text. We use comments to communicate with QA as content passes through the workflow. Not being able to comment on snippets is a real blocker - we cannot ask questions to QA, and QA in turn cannot alert us to content issues.

In the Advanced WYSIWYG editor, when using the “Add Link” option, previously used search terms in the dropdown overlap with the article list, making it difficult to view or select articles. Users currently need to manually remove each old search term to see the list properly. A feature enhancement is requested to either allow users to clear previous search terms easily or reposition the dropdown/dialog box so it does not interfere with the search results.