Feature Request

Currently, the Export feature is project-specific, which results in the following limitations: 1) Only one user can perform an export at a time. 2) Exported files generated by one user are visible to other users, even if they have different access levels. This poses a potential security concern. 3) In projects with a large number of Team Accounts, it is not ideal for users to wait for one export process to complete before initiating another.

In the current implementation of project exports, replicated articles are excluded from JSON and HTML exports to avoid duplication. One of our customers replicates a selected set of articles from multiple categories into a specific category for organizational purposes and exports this category in HTML; however, due to the current implementation, the exported file is empty. Requesting an option to include replicated articles in exports to support this use case.

Currently, if we schedule an article for publishing in Doc360, the editor does not allow us to make any changes to it. For any other instance, like when an article Workflow Status is in review, the changes can be made in real time. However, the only time the editor locks us out is during a scheduled publish. We want the ability to edit a scheduled article without having to move it to draft first. This increases the time to switch to draft and then schedule it afterward. Ideally, it should be smooth sailing as long as the article is unpublished. For example, in Slack, we have the option to edit scheduled messages without having to change their state. Once the editing is done, the user clicks the checkmark icon, and the updated message is locked for sending.

I'm frustrated that you cannot turn off the floating Eddy AI editor toolbar now when you're creating an article. Whenever I highlight text to make an edit, the toolbar covers up half of the text I'm trying to edit, and you have to click all around to get it to disappear, or press the Esc key to hide it. I wish you could just turn it off entirely, because I never need this level of granular control with every single mouse click. Just make the toolbar remain static at the top of the page, please

We sometimes experiment with different formats to present condensed information, like descriptions of UI elements. It would be extremely helpful if the conversion could be done with a simple click: "Convert to table", "Convert to tabs", Convert to accordions". In the case of accordions, because they are separate units, the conversion from accordions to tabs or table could be accomplished with this existing feature request: https://feedback.document360.com/feature-request/p/checkboxes-to-multi-select-text-blocks .

1) ACCORDION STYLING SETTINGS - such as for FAQ accordions for easier detection: Accordions are for most readers hard to detect due to the fact that the sections are just as white as the surrounding. And, that the small expansion arrow symbol is located at the far right. To avoid having to add explanations such as ”In this expandable section you find …” we would appreciate being able to make settings such as you today offer for FAQ accordions. 2) STYLING SUGGESTIONS - as settings mentioned above or as a stylesheet template: Position the expansion arrowhead to the left Make it more visible by making the it arrowhead bolder. Possibility to add a background color and / or a border color to the accordion heading section. 3) ACCORDION NAVIGATION / LINK BEHAVIOUR Where accordions are used for long nested descriptions, we also use accordion within accordions. Primarily as a nifty way to narrow down use case pages with long script samples, and to separate the top mandatory code from the lower-level optional code variants. This calls for better built in navigation assistance. And, that links are handled in search. When a search result include content in an accordion this accordion must be opened and the searched value must be highlighted. 4) ACCORDION HEADING NAVIGATION SUGGESTION In this example the top level accordion is with H2 heading and the sub-accordions are H3. This is the desired behavior when using the right-side table of contents called ”In this article”: No accordion should be expanded from the beginning. When the user selects H2 heading it should open that accordion. When the user selects an H3 heading it should open the master H2 accordion AND the H3 level sub-accordion. Or at least let the link move the cursor position closer to the approximate area …

When I highlight a word to add a link, chances are that I want to link an article/heading with this exact wording or at least containing this or a similar word ("Buchungsbelege" in the screenshot). However, I always have to search manually for the article because the current article is listed by default ("Debitoren - Übersicht" in the screenshot). There should be some intelligence built in that understands the context of what I'm linking, or perhaps a setting or option that lets me select if I want to link within the current article or by context (highlighted word).

Several key features such as the Floik step by step guide, duplicate content detection, and the AI glossary generator are currently not usable due to limited language support. Adding support for English (US) and additional languages would allow customers to fully use these features as intended. This enhancement would significantly improve feature adoption and overall product value.

Based on an earlier FR, Doc360 exports now support table of contents linking and allow entire categories, including subcategories and nested articles, to be exported together. The linking works as expected for navigation from the TOC. --- The issue arises with links inside the exported articles themselves. When one article in the export links to another article that is already included in the same export, the link does not navigate to that article within the exported file. Instead, it redirects users to the KB Help Center version of the article. This breaks the offline or self-contained nature of the export. If all referenced articles are already part of the export, internal cross-references should resolve within the exported document, not redirect to an external URL. Redirecting to online help is reasonable for links that point to: External websites such as Microsoft documentation. Articles in categories that are not included in the export. However, for links between articles that are already included under the same exported category or subcategory, the expected behavior is internal navigation within the exported file. --- For exports that include multiple related articles, we want: Cross-links between those articles are internalized automatically. Clicking a link should jump to the corresponding section or article within the export. External redirection to only occur when the target content is not part of the export. This ensures the export remains usable as a standalone document and supports offline consumption without loss of navigation context. --- PS: The export referred to here is PDF, not HTML export. The FR referenced is https://feedback.document360.com/feature-request/p/pdf-export-enhancements

I would like to have numbered step-by-step instructions with bullets as nested elements, then continued numbering. Example: 1) To do this, choose one of these 2 options: (first indented bullet) (second indented bullet) 2) Next, do that. 3) etc.