Feature Request

We would like to request that user list dropdowns be displayed in alphabetical order across multiple areas of the application, such as the user list in the workflow assignment section. This would make it easier to find and select the required user.

When an automated account email such as a password reset does not arrive, there is currently no way to tell whether it was sent, delayed, or failed, leaving the reason for non-delivery unclear until the issue resolves on its own. Add a delivery status indicator (sent, queued, or failed) for outbound account emails like password resets, and automatically retry sending if the first attempt is delayed or fails. Benefit: Users get a clear, immediate signal about the status of their reset request instead of waiting and guessing, and regain account access faster when delivery issues occur.

Currently, inline commenting is limited to the Draft stage, which restricts reviews after publishing. Enabling this would help reviewers share suggestions or highlight required updates when they notice issues later. This would reduce the need to move articles back to draft and support a smoother post-publish review workflow.

When groups are synced from an identity provider via SCIM, administrators currently have no way to confirm whether members were successfully mapped to the corresponding reader or user group, making mismatches hard to detect. Suggested Enhancement: Add a sync status view or log showing per-group provisioning results, including any members that did not map to the expected group after a sync. Customer Benefit: Administrators can confirm group assignments succeeded immediately after a sync and can identify and resolve mismatches directly, without repeated manual re-provisioning attempts.

When a user's session times out, they are returned to the login page and must manually re-select their SSO login option, even though they remain authenticated with their organization's identity provider. They are not returned to the page they were viewing before the interruption. Suggested Enhancement: Support silent re-authentication with the identity provider when a session expires, and preserve the originally requested page or deep link so the user lands back where they were once re-authenticated. Customer Benefit: Reduces interruption and manual steps for users returning to an active session, particularly for organizations that use the knowledge base site as a default working environment.

When a reader closes or cancels the feedback panel after clicking Like or Dislike, the reaction icon can remain visually active even though nothing was submitted. After a page refresh, the icon can still appear active because its state is stored in the browser rather than reflecting what was actually recorded. Suggested Enhancement: Sync the visible reaction icon with the actual recorded/submitted state, so it only shows as active when the reaction has genuinely been captured, and reset correctly when local browser data is cleared or the underlying record no longer exists. Customer Benefit: Readers and reviewers get a reaction indicator that accurately reflects what was captured, removing ambiguity about whether their input actually went through.

Bulk import of users or readers currently rejects entire rows outright when a name field contains a hyphen or other special character, requiring manual cleanup and re-upload before the rest of the batch can succeed. Suggested Enhancement: Automatically strip or flag unsupported characters in name fields during CSV validation, allowing the import to proceed (with a warning) rather than failing the row. Customer Benefit: Bulk onboarding of large teams completes in fewer passes, with less manual CSV editing required.

Team members who receive a project invitation email are taken to the identity server login page, where they must manually enter a subdomain before reaching their organization's identity provider. This adds a manual step for every new team member, even when a single sign-on configuration is already fully set up. Suggested Enhancement: Allow the invitation email link to route directly to the configured identity provider (using the existing IdP-initiated sign-in mechanism) instead of the intermediate subdomain-entry page, at least for projects with only one active SSO configuration. Customer Benefit: New team members reach their organization's login screen in one click instead of navigating an extra identification step, speeding up onboarding for large teams.

When an attempt to add a user fails because the email address is already associated with an existing account in a different role, the system can return a generic processing error rather than a message that identifies the actual cause. Suggested enhancement: Return a specific, actionable error message when user creation fails due to an email already existing under a different role, distinguishing this case from other request-processing failures. Benefit: Admins can immediately identify and resolve account conflicts on their own, without needing to contact anyone to interpret a generic failure.