• Member Experience
• Consent to add external videos to posts
• Administrator Experience
• Enabling languages
• Localized Communities
• Configure Multi-auth sign-in options
• Developer Experience
• Aurora Analytics
• Multi-Auth Admin
• You found it. We fixed it.

Member Experience

Consent to add external videos to posts

To further comply with the latest privacy regulations, we have introduced a new enhancement to view external videos on the community. We have prioritized member’s compliance by ensuring that external video providers cannot drop cookies without explicit user consent. 

Members are now required to explicitly consent to the use and storage of third-party cookies from external video providers before streaming content on the community.

This measure ensures that both community and external video provider cookies comply with regulations, protecting member data and maintaining compliance standards.

Note: This feature is set by default. If you want to change the default settings, contact Support.

Below is an example of how this banner appears when you add external videos to blog posts.

Administrator Experience

Enabling languages

From Designer, you can define which languages are used in your community. You can also set which language to use by default. English is set as the default language for all new communities.

Note: At this time, English and Spanish are the supported languages in Aurora. More languages will be available in a future release.

To enable additional languages in your community:

1. Open the Account menu and go to Designer > Community Text.
2. In the row of Enabled languages, click Edit.
3. Use the Add language drop-down menu to select languages you want to be available in your community.
4. Click Save.

For more information, refer to Enable languages in your community.

Localized Communities

Administrators can now create localized communities by creating top-level categories to house content in different languages. Each of these localized categories is mapped to a particular language in the admin area.

To enable Localized Communities for your community, open a Support ticket. Then, you can create a category for localization the same way you would to create any other category. We recommend that you set up your localized categories on a stage environment before setting them up on your production environment. Doing so enables you to reference the stage setup during the production setup for a quicker configuration process. Additionally, if your production community is already live with your customers, we recommend that you set up your localized categories during non-peak activity hours.

After creating the category, you map it to a language you’ve enabled in your community.

Note: At this time, English and Spanish are supported. More languages will be available in a future release.

After you map your top-level categories to the languages you have enabled in your community, your customers are directed to the language category that best matches their browser language. However, as a secondary measure, they can use the language selector to change languages.

Note: Member-generated content is not translated into any other languages.

Learn more about Localized Communities, how to create and map them, and how to configure their settings.

Configure Multi-auth sign-in options

Communities require diverse authentication methods to accommodate varying user segments like employees, customers, etc. This involves supporting sign-in via multiple SSO providers or different types of SSO such as OIDC, SAML, etc.

With this release, community admins have the flexibility to configure multi-authentication settings autonomously. They can enable desired authentication mechanisms including native community sign-in, Khoros SSO, SAML, OIDC, and more. Additionally, they can customize the sign-in window by choosing which options to display and rearranging their order to suit specific user segments such as employees, customers, etc.

To enable this feature in your community, contact Support. After the feature is enabled, you can see the Sign-In Display option under Settings> Systems > ACCOUNT > Sign-in.

Edit the Sign-In Display option to configure the sign-in options you want to provide your users and how you want to display the sign-in options.

Below is an example on the list of sign-in options you can configure. 

From here, you can:

• View all available sign-in options for your community.
• Add a welcome note that will be displayed when users are on the sign-in page.
• Turn on or off the sign-in options you prefer.
• Edit the labels of the sign-in buttons.
• Rearrange the order in which the sign-in options appear on the sign-in pages.
• Choose to display the sign-in options as buttons for member sign-in.
  If you select the Display as sign-in button option, members will see a sign-in button.

   

If you de-select this option, members see a sign-in form instead.

Learn more about Multi-auth admin.

Developer Experience

Aurora Analytics

The Aurora Analytics API enables Aurora customers to request metrics and reports that are currently available in the Aurora Analytics user interface (UI). The Analytics API also offers on-demand insights such as the total number of fully registered members who are not deleted or banned.

Learn more about Aurora Analytics.

Multi-Auth Admin

With this release, we have updated the multi-authentication mechanisms to do the following tasks:

• Retrieve the provider details for each authentication mechanism
• Create the new specific settings for Khoros SSO
• Configure the multi-authentication options

You found it. We fixed it.

• Previously, the search field did not open in some communities when you scrolled down the page and clicked the search icon. We have resolved this issue.
• Previously, the automatically generated SP Metadata single logout service URL did not include the community ID. Now, this URL includes the community ID as expected.
• Author information that appears at the bottom of a post previously included the default avatar for the current place even when a different one was configured. Now, the avatar that was configured for the current place is displayed as expected.