Member Experience

Performance improvements

As an ongoing improvement to community performance, we optimized several general components across the application.

My Settings: Language

On the My Settings page Preferences tab, under Language, the Community language drop-down menu now includes the Browser Default option. Your browser stores your preferred language, and by default, the community uses your browser preferences. If you change the language in your settings, you can override the browser default for your account.

If you selected a language in this drop-down menu prior to v25.02, your selection is retained.

Refer to Manage community preferences for your account to learn more about your settings.

Content Workflow notifications

As a community member, you can now receive content workflow email notifications when someone completes the following actions:

• Edited or saved a draft
• Submitted a draft for review
• Submitted a draft for publication
• Recalled a draft
• Scheduled a draft for publication
• Returned a draft to its author
• Returned a draft for review
• Updated the publication schedule for a draft
• Canceled the publication schedule for a draft
• Added you as a co-author
• Removed you as a co-author

The New Follow (Digest) and New Follow (Immediate) email notifications also contain content workflow updates.

To manage these notifications, refer to Manage Follow and Notification preferences for your account. For a list of all possible email notifications, refer to About Aurora Email Notifications. By default, Co-authors receive the notifications workflow updates Immediately.

Admin Experience

Designer: Search Results Page template

Community designers can now customize their search results page using the Search Results Page template. This enables communities to promote the content, places, and people that are the most relevant to their community members’ needs. Updating the look and feel of this page template also encourages cohesion in branding across the community.

This page template includes the following four widgets out of the box that cannot be deleted:

• Search bar widget (with filters)
• Content Results widget (shows content matching the search query)
• People widget (shows people whose usernames match the search query)
• Places widget (shows places with names matching the search query)

To update this page template, open your Account menu, go to Designer > Page Templates, and select Edit on the Search Results Page. For more information about this page template and others, refer to About Aurora Page Templates. For configuration information, refer to Using Aurora Page Templates.

Salesforce connector upgrade

Currently, when you integrate a community with a Salesforce application, the authorization request from Salesforce may fail if the Salesforce’s IPs are not allowlisted in the community.

With many upgrading to Salesforce Hyperforce, where Salesforce IPs change dynamically there is a risk of  frequent integration failure.

To mitigate this risk, we have upgraded the Salesforce connector to version 4.4 . 

Now, the authorization request originates from the Salesforce to authorise the Salesforce Integration API App configured in the community. After the authorization is successful, the access and refresh tokens are verified and stored in Salesforce. This ensures a stable and seamless integration.

Note: 

• Contact support to add the required configs in the configuration file.
• The authorization needs to be performed by a member with elevated permissions, for example, an Admin.

Learn how to enable the new connector.

Media moderation

To help maintain a safe and compliant environment in your community, we have introduced the Default Media Status setting to review content with media (includes images, videos, and attachment files).

You can find this setting under Settings > Moderation > General > Default Media Status.

The screenshot below shows this setting at the community level.

Media moderation can be configured at both the category and board levels, with board-level settings taking precedence over the parent category.

When you try to publish a post that contains media, the moderation settings for both content and media are checked. The post’s visibility depends on the moderation rules applied. 

For example, in the “Pet Lovers” forum settings shown below, text content moderation is set to Auto-approve, while media status is set to Required. This means any post containing media is published only after the media content is approved by moderators.

When members (without Bypass moderation permission for Media) try to publish a discussion in the forum, they receive a notification that the post requires approval and is not visible in the community.

Moderators can approve or reject the post from the Moderation tab in the Manage Content dashboard.

Note: Media moderation is available for:

• • Discussions and their replies
  • Blog comments
  • Knowledge base comments
  • Ideas and Idea comments
  • Event comments

To facilitate faster search results while moderating content, we have introduced a filter for media in the Moderation tab in the Mange Content dashboard. 

Media Moderation Bypass feature 

Along with the media moderation feature, we are introducing the Bypass moderation permission, allowing trusted members to post media (includes images, videos, and attachments) without requiring moderation. This ensures a smoother experience for verified users while maintaining content control for the broader community.

You can find this permission under Settings > Moderation > Users > Media.

Activity limits

We've introduced the Activity Limits settings to limit rapid actions like publishing, commenting, or private messaging within short intervals in your community. For example, if a member attempts to publish, send private messages, or post images too frequently, they are temporarily restricted, ensuring the community remains focused on meaningful engagement rather than automated or disruptive behavior.

You can find this setting under Settings > Moderation > Activity Limits.

Below is a screenshot of Activity Limits feature options:

Note: The Bypass flood control permission that was introduced in Aurora version  24.12 is now renamed to Bypass activity limits.

As shown in the screenshot above, there are three sections under Activity Limits:

1. Default Limits: These limits are set at the community level and apply to all members.
2. Role-Based Overrides: You can specify roles from your community and set different activity limits. This helps you manage user engagement by applying stricter limits to new members until they earn a certain role or rank. For members with these roles, the limits defined in this section override the default limits.
3. Role Exclusion: You can specify community roles whose members should be exempt from activity limits. These are trusted members, most often Admins and Moderators. When added, all members with these roles are automatically granted the Bypass activity limits permission. When removed from here, this permission is set to Deny.

For Default Limits and Role-based Overrides, the activity limits include: 

• Posts: Specify how many posts members are allowed to publish in 30 seconds, 10 minutes, and in 1 hour.
• Private Messages: Specify how many private messages members are allowed to send in 30 seconds, 10 minutes, and in 1 hour.
• Images: Specify how many images members are allowed to publish in 30 seconds, 10 minutes, and in 1 hour.

Learn more about Activity Limits.

Analytics: Thread ID filter

We have introduced a new filter called Thread ID. You can use this filter to view the metrics related to a particular thread or topic in your community. The Thread ID is the ID found at the end of the community URL. 

For example, in the below URL, “236502” is the Thread ID for a topic in the community: "https://community.khoros.com/kb/supportinformation/khoros-cookies-datasheet-community-care-marketing-khoros-bot/236502".

You can add this filter under Dashboard and Reports by selecting the Filter option.

You can add more than one Thread ID to the filter. 

After you select Add, the dashboard displays the metrics for the added Thread IDs or, in other words, the topics with those Thread IDs.

Learn more about filter options.

Developer Experience

Message Constraints GraphQL Updates

With this release, we have added the following update to the message constraints:

• hasVideo constraint to show the messages that have videos
• hasImage constraint to show the messages that have images
• hasAttachment constraint to show the messages that have attachments.

Bypass Media Moderation Permission

In this release, we have added a new bypass media moderation permission that allows members to post content with media such as images and videos without moderation.

Note: Only Administrators and Moderators have access to this permission.

See Working with Bypass Media Moderation for more information.

Media Moderation Setting

In this release, we have added a new mediaModerationStyle setting to enable members to post content with media such as images, videos, or attachments. Based on this setting value, the post will be sent for moderator review. 

See Working with Media Moderation for more information.

Optimize Your Community Experience

To optimize your community developer experience, we introduced an ability to add JavaScript files for handlebars and HTML components.

With this, you can use Page Scripts in both the handlebars and HTML components to render your component.

See Adding Javascript files to HTML and Handlebars Component for more information.

Additional Policies for Content Workflow User Notification

In this release, we added three additional policies for content workflow user notification actions:

• canAccessCWAAuthorNotificationSetting
• canAccessCWAEditorNotificationSetting
• canAccessCWAPublisherNotificationSetting

See Using the Content Workflow for more information.

Updates to Aurora Handlebars Helpers and Context Objects

We have updated the Khoros-provided Handlebars helpers and context objects you can use for your Custom Handlebars Components.

These updates include new helpers for GraphQL queries, localized text strings, category and message lookups, and more.

See Handlebars Helpers and Context Objects for more information.

Allowed Dependencies for Custom React Components

In Aurora version 25.02, we introduced validation to the build to ensure that only allowlisted dependencies already installed by Aurora are used for custom React components.

The following dependencies are currently allowlisted and can be added to a custom React component if needed:

• react
• react-bootstrap
• react-hook-form
• react-uid
• react-dropzone
• moment-timezone
• @coveo/atomic-react
• @coveo/atomic
• @coveo/headless-react
• @coveo/headless

See Allowed Dependencies for Custom React Components for more information on this update and how to add additional dependencies to future Aurora releases.

You Found It. We Fixed It.

Search

• All content types that are enabled within your community can now be selected from the drop-down menu on the community's Search page.
• The search bar in the +tag button works as expected, with the keyboard appearing properly and enabling tag searches.
• The userSearch query with the searchTerm field no longer breaks the GraphQL API.

Ranks

• You can now move a rank to the top of the rank list as expected.

Localization 

• The display issue that occurred for some languages when creating a custom ban time has been resolved.
• In localized communities, external links added to the navigation bar are now updated in the expected language’s JSON file. 

Images

• Image upload metrics are now respected in Badge criteria.
• When you add an image asset to a react component, turning off the SDK and merging via GraphQL API, the react component is now rendered properly.

Videos

• Video uploads with filenames containing JavaScript scripts are now validated and blocked, preventing potential security risks.
• You can no longer upload a video that triggers a JavaScript message when you view it on the From My Videos tab.

Attachments:

• You can now add .cmd attachments to posts. 

Ideas

• When you select the Show more button on the Ideas board, all replies are immediately displayed.
• When an Idea with more than 3 threaded replies is moved to another board, all replies are also successfully moved along with the Idea to the destination board.

Knowledge base

• Read-only knowledge base articles are no longer editable by general members.

Replies and comments

• You can now edit events even when comments are turned off.
• When you add nested replies to a post and generate a permalink, those replies are no longer duplicated.
• As expected, members can now mark only one reply as a solution, as opposed to marking multiple replies as solutions.
• On the permalink page for a comment, you can now add or remove a solution as expected.

Rich Text Editor

• When you add an invalid color option in the advanced table properties in the content editor, the previous color is now saved instead of the table reverting to the default settings.
• When you migrate your community from Classic to Aurora, the Table of Contents (TOC) now retains proper styling, including correct indentation and list formatting.
• Various fixes were made on the editor, including UI, on the text formatting, toolbar functions, media insertion, accessibility, and keyboard navigation.

A11y

• When mentions results match multiple keywords, keyboard navigation now works as expected.

API 

• Members can now successfully create, update, or delete custom entity fields using GraphQL API.
• The rate-limit issue of the Github API with the repository has been resolved.
• The userLink react component now generates links without UID.
• Color values for links and buttons changed via GraphQL are now respected in email templates.