Feature Request

Currently, the editor supports indentation only for regular text, while tables and callouts cannot be indented. It would be helpful to extend the existing indentation functionality to these elements as well, allowing users to maintain consistent formatting and visual hierarchy throughout their documentation.

Currently, when placing a Tabs component inside an Accordion, the tabs are not clickable inside the portal. This feature request proposes adding official support and guidance for embedding Tabs within an Accordion panel, ensuring smooth interaction, visual consistency, and reliable state handling.

This request was created on behalf of Kristopher At this time, the entire table width is resized usign 'Fit to width'. We want each column should be sized based upon the content of all of the rows (not equally sized within the table's space). Thank you.

There is no ability to mark individual table cells as private or hidden from end users, and conditional content cannot be applied to specific cells. As a result, authors must duplicate tables or split content into multiple tables, making documentation harder to maintain and increasing the risk of inconsistencies. Conditional Content rules to be applied to individual cells instead of requiring the entire table. Thanks.

We were able to link the headings inside the accordion with the old link popup. In the new link popup modal, we were unable to link to a heading within accordion / FAQ. It would be great to have this functionality included as well.

Issue: When uploading a large file in the article editor, the UI gives no feedback during upload — the screen appears idle with no progress indicator. The user only discovers the upload failed after waiting, when an error toast appears: "Failed to read the request form. Request body too large. The max request body size is 157286400 bytes." Problems with current behavior: No progress indicator or spinner during upload, so users can't tell if anything is happening. No upfront indication of the max file size (150 MB) before the user selects/attaches a file, failure is discovered only after the wait. The error message exposes a raw byte value (157286400 bytes) instead of a human-readable size (150 MB), which is confusing for non-technical users. Suggested fix: Validate file size client-side before upload starts, and reject immediately with a clear message (e.g., "File exceeds the 150 MB upload limit. Please upload a smaller file."). Display the max upload size limit near the upload/attach control proactively. Show a progress bar or loading state during upload so users know the action is in progress. Convert any byte-based limits in error messages to human-readable units (KB/MB/GB). Impact: Users waste time waiting on uploads that are destined to fail, and the technical error message creates confusion and support tickets.

When adding hyperlinks within an article, the article selection list truncates long paths using ellipses (…). This makes it difficult to distinguish between articles that share the same title but exist under different categories or subcategories. Displaying the complete article path (category → subcategory → article) on mouse hover would help users clearly identify the correct article while hyperlinking, especially in large knowledge bases with deeply nested structures or duplicate article names.

Tab names over a certain length are truncated. It would be nice if they just wrapped. Also, the left/right arrow navigation that appears when more than six tabs are present is a little awkward: both left and right arrows are always present even when navigated all the way to the left or right.

The customer requested an enhancement in the article review workflow where reviewer inline comments inside collapsed accordions or hidden tabs should automatically become visible. At present, users must manually navigate through accordions and tabs to locate comments, which creates confusion and affects the review experience.

I want to be able to store defaults for table dimensions, e.g., so that all my newly created tables have the same columm widths. Also, I want to be able to store default width and height sizes that are applied to all newly added images.