Administrator Experience

Review content reported by content filters

Community content filters identify inappropriate words used in community content and take appropriate actions on the content based on how you’ve configured the filters to behave. Any posts and replies, private messages, profile information, tags, and usernames that are flagged by the content filters are sent to the Manage Content page Abuse tab, where members with the appropriate permissions can review and take actions on them.

Each item that has been reported shows the Title, Author, Date Reported, Filter name, and Filter action.

Depending on the content type, you can edit a piece of content to remove any offensive language, mark content as spam, confirm content as abuse (which then removes it from the community), ignore the report (which leaves the content in the community), and/or ban the offending member from the community. The table below shows which actions you can take on which types of content.

Content Type	Filter Action	Moderator actions on the content
Forum discussions/Blog posts/Knowledge Base articles/Replies	Replace term/None (Take no action)	Edit Mark as Spam Confirm Abuse Ignore Report Ban Member
Forum discussions/Blog posts/Knowledge Base articles/Replies and Private Messages	Blocked/HTML Blocked (Do not allow/Check Inline HTML and do not allow)	Ignore Report Ban Member
User Registration	None (Take no action)	Ignore Report Ban Member
User Registration	Blocked/HTML Blocked (Do not allow/Inline do not allow)	Ignore Report

To learn more, see Review content reported by content filters, About content filters, and Set up content filters. 

Custom widgets

We now provide the ability for Aurora communities to offer custom widgets. These custom widgets can address use cases or functionality not available in out-of-the-box widgets. Custom widgets are created using components in the Dev Tools (SDK) but can then be added and configured in the Designer area of Admin. 

To access and configure a custom widget:

1. In Designer, open the page template to which you want to add the custom widget.
2. Add a widget section by clicking the add icon (plus sign) in an open area of the page template. 
3. In the Add Widget panel that opens, locate and select the custom widget you want to add. It may be located under any of the categories (Content, People, or Places) depending on what it is related to. If a custom widget has not been tied to any categories, it is located under Other > Custom.
   
4. Configure any or all of the following: 
   • Widget Title – Sets the title that appears at the top of the widget. If the Visible only to screen readers option is turned on, the title remains hidden to most visitors; however, the title information is still relayed to visitors using screen readers.
   • Remove widget background – If you turn on this option, the background of the widget is removed, which allows the section background to show through instead.
   • Visible To – Select whether you want the widget visible to Both Non signed-in and Signed-in users, Only Signed-in users, or Only Non signed-in users. 
   • Optimize page-load time – Optimize page-load time by utilizing lazy load functionality, which loads images as the member scrolls down the page.

Read more on getting started with widgets and custom widget configuration.

SAML support

With the release of 23.7, Aurora communities can now be set up with SAML (Security Assertion Markup Language), a form of SSO (Single Sign-On). SAML passes SSO authentication data from an identity provider to a service provider. This XML-based protocol uses security tokens containing assertions to pass information about an end user between the SAML Identity Provider (IdP) and SAML Service Provider (SP).

We’ve provided SAML configuration options in the Aurora Admin that enable you to set up IdP-initiated SAML or SP-initiated SAML. To access these settings, go to Admin > Settings > System > Account. Here, you can turn on SAML and configure required basic settings, IdP settings, assertion to profile mapping, SP metadata settings, sign-in settings, sign-out settings, and other advanced settings related to SAML. 

Learn more about Aurora Security Assertion Markup Language (SAML) Single Sign-On (SSO), how to configure SAML for the Aurora community, and SAML settings.

Switch Member actions in Audit Log

If a community member with the Switch to another member permission switches to another member and performs an action, the Audit Log now shows which member switched to another member, the member they switched to, and what actions they took while acting as the member they switched to.

See Using the Audit Log and Use the Switch Member feature to sign in to a different Aurora community account for more information.

Developer Experience

Handlebars Component Support

Aurora now supports Handlebars components that you can add to your page templates. Custom components written in either HTML or Handlebars share the same components directory in your Git Repository. All resources for these types of custom components live in a directory in your Git Repo.

While you can add HTML components via the Page Templates area in the Aurora Designer, you must commit and push Handlebars components directly to the Git Repo from a developer's component or a GraphQL mutation called to create the component.

Refer to our Handlebars component documentation for more information about:

• How to create a Handlebars component
• Styling a Handlebars component
• Helpers and context objects that are available to use in your Handlebars component

API Tutorials

To enhance the developer experience, we have added the API tutorials to provide a real-world scenario. 

In this release, we are providing the following:

• Using the Content Workflow Action (CWA)
• Retrieve the abuse reports by member
• Retrieve the abuse reports by content filter