Announcement

Enhancing security with AWS Bot Control

To strengthen the security of our communities, we are rolling out AWS Bot Control for all Classic and Aurora Communities customers this month. This advanced feature is designed to block unwanted bot traffic, preventing your platform from performance degradation.
We’ve conducted thorough testing to ensure a seamless deployment with minimal impact on the end-user experience and is implemented without any associated downtime, ensuring uninterrupted access for all users.

Member Experience

Community languages

Community pages and email notifications are now available in English (UK), Chinese (Simplified), Norwegian, Swedish, Spanish (Mexico), and Korean.

Refer to About Aurora community languages for more information and a full list of available languages.

Admin Experience

Community Guidelines & Privacy Policy

Admins can now enable community guidelines and privacy policies for their communities. These can be linked to an external URL or built within the Aurora community itself. Depending on what you’re going for, building your guidelines or privacy policy within Aurora creates a seamless experience with consistent branding, while linking to an external URL enables you to use one central location where these documents live so you don’t have to update them in multiple places.

After the community guidelines and privacy policy are created, admins can also designate these as required reading for registration and/or provide a link on the registration window for new members. 

For communities in multiple languages, you can provide guidelines and policies in all your available community languages to ensure that all members of your community are aligned on expectations and security regardless of language.

To learn more about creating and enabling these documents, refer to Configure community guidelines and Configure privacy policy.

Content Archive

We’re excited to introduce the content archival feature in this release!

Admins and moderators can now effortlessly maintain community hygiene by reviewing and archiving content that is no longer accurate, timely, or relevant.

While this feature is enabled for all communities by default, you can manage the feature’s enablement  on the Content Archive option under Settings > Features > Moderation > Content Archive.

Note: This feature is set only at the community level. 

Admins, moderators, or members with the Manage content archival permission can archive community content.

With the appropriate roles or permissions you can: 

• Archive content directly from the Options menu for any content type.
• Add a link to a community or external page to redirect members to related content.

 

• Access the Archives tab in the Manage Content dashboard to view, unarchive,  and manage all archived content in one place.
• Search for archived content using filters.

Learn more about Content Archive. 

Conversation display formats

Previously, replies and comments on community content were displayed exclusively in a threaded format, where all replies (or comments) appeared in the context of the main reply (or comment).

In this release, we’ve introduced an option to display replies and comments in either a linear or threaded format, allowing you to tailor the conversation view to better suit your community’s needs.

Admins can set the Display format to Linear or Threaded from Settings > Content Features > Replies and Comments. 

Note: This can be set at the board level. When the board-level settings are different from that of the community level, you are notified of the override with a label.

Below is an example of conversations displayed in a linear format.

Below is an example of conversation displayed in a threaded format.

Learn more about linear and threaded replies. 

Developer Experience

Updating Conversation Formats

In addition to introducing the Admin experience for setting a default conversation format, this release also includes GraphQL support to update the place (node) or user conversation to either linear or threaded format.

Learn more about Setting the Replies Format.

Content Archive

In addition to the Admin experience to archive a message, we also provide GraphQL support to archive and unarchive messages

Learn more about Working with Content Archive.

Email Styling

In the previous release, we introduced GraphQL support to update the email template. With this release, you can add styling, such as changing the font colors of the email and styling the email buttons.

Learn more about Styling the Email.

JWT SSO Support for Multi-Authentication

We introduced the JWT SSO authentication in the 24.09 release. With this release, you can add it to your multi-authentication mechanism.

Learn more about Configuring the Multi-authentication Mechanisms.

Multi-theme Support via GraphQL

You can now use the GraphQL API to apply multiple themes to your Community by assigning different themes to specific places (referred to as nodes in the API). Theme assignments are automatically inherited by child places.

Find out more about Multi-theme Support.

You Found It. We Fixed It.

Abuse Management

• Admins can now ban members from the Content Management dashboard Private Message tab as expected.

Case Portal

• Members no longer see a blank screen and can now successfully use the My Cases option in the Account menu to create a support case.

Inbox & Messaging

• Broadcast messages no longer have a recipient limit.
• When you send a standard private message to a number of recipients that is higher than designated in the admin settings, you receive an error message that indicates the allowed number of recipients.

Member Registration

• Administrators can now add hyphens (-) and underscores (_) to usernames without receiving an error.
• Custom fields now consistently appear during registration.

Permissions

• The Manage ideas and comments permission is no longer required to update an idea’s status. Now, only the Change idea status and Read ideas and comments permissions are needed.

Posts

• On a post, when you select the latest timestamp that is related to a comment, you are now taken to the list of comments sorted by Newest as expected.  
• The Create Post button on Ideas, Events, and Blog pages no longer mistakenly directs you to create a discussion.
• When you mention a member in a post, text you include after the mention is no longer included in the mention, and the comment no longer disappears.

User Interface

• Hover text now appears as expected when you hover your cursor over the Settings and Follow icons.
• The navigation bar is now updated to show that the user is signed into the community.
• Error pages now reliably display the correct text.

Widgets

• The options in the Event Type filter on the Event widget are now selectable as expected.
• You can now successfully edit the Featured Places widget in Google Chrome.

Developer Experience Fixes

• Incorrect page script identifiers in the groups.scripts.json file no longer triggers an internal server error.
• The switch branch feature is fully operational, and SDK preview is accessible for branches that have been pushed to Git. However, SDK preview is not yet available for local changes that have not been pushed to a branch. We are actively working on enhancing this functionality in an upcoming release.