Feature Request

When tables are bugger than the fold and you scroll down, you cn't see the table headers. Allow me to decide, for each table, whether to lock the table header.

When dealing with articles that contain confidential or sensitive information, ensuring controlled access is critical. Currently, if an editor generates a private link using the "Share Link" option, this link can be accessed by anyone who has it, potentially exposing the content to unintended viewers. To enhance privacy and security, it is essential to introduce restrictions on who can generate these private links. Customers should have the ability to configure role-based permissions, ensuring that only authorized users, such as admins or designated roles can create shareable links. Additionally, a built-in expiration mechanism should be implemented for these links. By setting a timeout for automatic expiry, owners of the project can minimize the risk of unauthorized access over time. This ensures that confidential information does not remain accessible indefinitely

Customer would like to resolve the issue with the "Block contains unsupported HTML tags" while converting from the WYSIWYG editor to the Advanced WYSIWYG editor."

The customer would like to explore the possibility of a feature that allows a private note to be converted into public content at the time of publishing. Use case: The team works on documentation updates for upcoming releases, which typically occur quarterly. All related documentation must be ready in time for the release. Currently, these updates are maintained in external tools like Word or Notepad and then copied into Document360 shortly before the release. If it were possible to add or update content directly within an existing Document360 article as a Private Note, and later convert it to public content just before publishing, it would streamline the process significantly. The customer envisions a simple action, such as a "Convert to Article" button, that would seamlessly transfer the private note content into the article’s public template.

Currently, when an unsupported tag is used in the Advanced WYSIWYG editor, it automatically generates a <editor360-custom-block> tag. This results in the need to manually update the content in the code view, which can be inefficient and error-prone. This feature request proposes a way to display unsupported tags directly in the editor, allowing users to identify and address them without switching to the code view.

I would like to have two tables next to each other, rather than stacked vertically. This can be done by manging them as blocks, or by making an empty column in a single table. However, if I make the border color white, this affects the surrounding columns.

Is there a way to prevent the categories and articles pane on the left side from collapsing each time I click on a different article while the toolbar/formatting bar is pinned? I have a large viewport with ample editing space and would prefer to keep the editor pinned without the categories collapsing.

This request was raised on behalf of Parthasarathy At this time, whenever team accounts were tagged in the inline comments, a notification is triggered. If the team account missed to check the e-mails, they won't notice that they're tagged in the article. It would be better if we highlight the dashboard whenever they're tagged in articles like we show notifications for release updates. Thank you.

Description: Currently, users can change fonts only through the formatting options on the right-side menu. There is no option to change the font using the quick insert menu or keyboard shortcuts. Requested Enhancement: Introduce keyboard shortcuts or quick menu options for font selection to improve efficiency and reduce the need for manual scrolling and clicking. This will streamline the formatting process and enhance the user experience.

We want to be able to generate links for headings within tabs. For example, if I have an H4 within a tab, currently, no link is generated for that heading. This makes it difficult for us to link content to that heading within the tab, however, we want to be able to link content within the tab.