Aurora: Set up content filters
In addition to the default content filters provided in Aurora, you can create community-level content filters and configure them to perform the appropriate actions in the respective areas across the community. Also, you can add terms to the existing filters or edit filter information, as required. View content filters Admins and members with permission can access the Content Filters in the Moderation settings area (from the Settings > Features > Moderation). The Content Filters tab includes the default filters as shown below: The Content Filters tab lists: Filter Name: Name of the content filter. Action: The action the filter performs when the system finds it in the community. Actions can be Do not allow, Replace term, Check inline HTML and do not allow, and Take no action. Term Count: The number of terms defined for the filter. You can edit and add terms to the default filters or add a new filter. When the number of filters in the Content Filters tab exceeds 25, you can use the Filter by name field to quickly find the filter you want. Add filter To create a new content filter: Sign in to the community as an Admin. Open the Account menu and go to Settings > Features. Select Moderation. In the left column, selectContent Filters. Select Add Filter. Enter the Filter name. Select a Filter action: Do not allow Prevents members from posting content or replies, registering to the community, adding tags, updating profile information, and sending private messages till the filter term is removed. This more heavy-handed approach runs the risk of either challenging members to find a way to defeat it or alienating them. Replace term Replaces the offensive term with another term. This is the most common way of handling smut filter infractions. You can configure what term to replace words that match this filter in the Replacement term field. Check inline HTML and do not allow Prevents the members from posting anything that contains a filtered term after ignoring inline HTML. Take no action Does not take any action on filtered terms that appear across the community other than sending to the Manage Content > Abuse tab for moderator’s review If the Filter action is set as Replace term, in the Replace with field, specify the replacement term. The content filter replaces the filtered term with this replacement term. If you want to set term-level replacements, you can edit the terms after creating the filter. In Apply filter to field, select the areas where you want the filter to be applied. You can apply the filter to content, private messages and invitations, username, profile information, and tags. (Optional) If you want the filter to treat terms with diacritic marks the same as those without (for example, “chëēse” would be interpreted the same as “cheese”), turn on Ignore diacritics. In Terms to filter field, enter the terms you want to filter. Note that you can enter only one term per line. SelectAdd. The new filter is added to the list of content filters. You can edit the filter information and can add more terms to the filter. (Optional) For the Replace term filter action, if you want to add optional replacement terms for a certain term, open the Options menu for that term, select Edit, and enter an Optional replacement term. If you do not specify the Optional Replacement Term, the term is replaced with the default replacement term specified in the Replace with field.Aurora: Edit a content filter
From time to time, you may want to update a filter action, apply a filter to other areas, or add more terms to a filter. From the Content Filters tab, you can edit the default filters or existing filters. To edit a filter: Sign in to the community as an Admin. Open the Account menu and go to Settings > Features. Select Moderation. Go to the Content Filters tab. Open theOptions menu and select Edit. The filter page is displayed with the Filter Information and Terms sections. The Terms section lists the terms added to the filter along with their respective Optional Replacement Term, if configured: From the filters page, you can: Edit filter information Add terms to a filter Edit or remove terms Edit filter information From the filter page, click Edit Info and update the required fields. Note that you cannot edit the Filter Name. Add terms to a filter From the filters page, go to the Terms section and select Add Terms. In the Add Terms window, enter the terms you want to filter. You can enter only one term per line. If you do not specify the optional replacement term, the term is replaced with the default replacement term. Click Add. The new terms are added to the list. Edit terms Sometimes, for a term added in any filter with filter action set to Replace term, you might want to add an optional replacement term or edit an existing optional replacement term. Note that you can edit only the terms that belong to the filter with Replace term action and not for other filters actions such as Do not allow, Check inline HTML and do not allow, and Take no action. To edit a term: From the filters page, go to the Terms section and click Edit next to the term. In the Edit Term window, add or update the Optional replacement term and click Save. The content filter replaces the identified with the optional replacement term in the configured areas of the community. Note that the content filter does not replace the content that is already identified and replaced with the previous optional or default replacement term. Remove filters From the filters page, go to the Terms section and click Remove next to the term. Remove terms of the filter with Filter actions set to Do not allow, Check inline HTML and do not allow, or Take no action: From the filters page, go to the Terms section and click Closenext to the term.About Aurora content filters
Communities are meant to be a safe space where members should feel welcomed and engaged. Sometimes, members post objectionable content that may offend other members and negatively impact the community’s overall health. Objectionable content can include inappropriate language or any other terms you might not want to see in the community. Aurora offers content filters as part of its moderation tools to prevent objectionable content from appearing in posts, replies, tags, private messages, profile information, and member registration. When members use inappropriate words across the community, content filters identify them and prevent the content from being published or replacing the words with pre-defined replacement terms. In other cases, content filters just record the objectionable content posted across the community without taking any action. Content filters can also be used to ensure that the correct words are used across the community to improve content consistency. For example, you could create a content filter to replace old product names with the correct product name. Aurora includes several default filters that can be triggered when someone registers, posts, adds a tag, sends private messages, or updates their profile information. Default Filter Applies to Filter action Smut Posts and replies Prevents objectionable language from appearing in posts. Replaces offensive terms with neutral or slightly humorous ones, if configured to do so. Remember, you don’t want to prevent members from posting messages; you just want to keep the language clean. You may want to have your moderators keep an eye out for members who repeatedly use filtered language. Keyword Posts and replies Manages specific words or phrases. Content for this filter may include product and company names—both your own and those of competitors. When filtered keywords are used in content, moderators are notified. Optionally, the terms are replaced with more appropriate or the correct term. Login User signups (Registration page) Prevents people from registering to the community with an inappropriate username or profile info (system default action). Note: The Login filter is not applied if you are using an SSO implementation that passes the person’s username to the community. You must have a system on your side to deal with this situation. Tag Tags added in posts and replies Prevents members from tagging posts with objectionable words. Replaces with an alternate tag if configured to do so. You can add terms to these default filters or edit default filters as needed. You can also add new filters to perform these actions when the filter terms are identified in the community: Do not allow: Prevents members from posting content or replies, registering to the community, adding tags, updating profile information, and sending private messages till the filter term is removed. This more heavy-handed approach runs the risk of either challenging members to find a way to defeat it or alienating them. When filter term is identified, the following error message is displayed: Replace term: Replaces the offensive term with another term. This is the most common way of handling smut filter infractions. You can configure what term to replace words that match this filter in the Replacement term field. When the filter term is identified, it is replaced with the configured term after you post the content. Check inline HTML and do not allow: Prevents the members from posting anything that contains a filtered term after ignoring inline HTML. For example, the term “crap” written in inline html format, “c<b>r</b>a<br>p” in any new post is identified as the filter term after ignoring the inline html. Take no action: Does not take any action on the filtered terms that appear across the community, but records in Content Filters dashboard to notify moderators about these terms used across the community. Tip: Replacement terms are often a better management strategy versus preventing members from posting, as some people might take it as a personal challenge and invest tremendous effort in attempting to circumvent your filters. Another way these members may try to circumvent your filters is by using variations of banned words. For that reason, you may want to plan ahead for possible misspellings or other variations when creating your content filters. Note: Content filters are not case sensitive. For example, to filter for “Test,” “test,” and “TEST,” you need to enter only the term “test” while creating the filter.About Aurora Analytics
To have a successful community, you need to know what’s working and what needs improvement. Aurora provides a robust set of analytics so you can get actionable insights to drive traffic and member engagement. You can determine what kinds of content needs improvement, what your members steer away from, and what they want more of from your community. These metrics help you learn where your members come from, what type of content they engage with, and where to focus on to reach new people. Having clear data enables you to plan towards community goals and make informed decisions to change course when things aren’t working. Aurora Analytics provides visual dashboards and interactive reports to provide you with high-level and detailed data on how your community is performing. Note: Currently, users can see the metrics up to the previous day in Aurora Analytics.. Data is reported in Coordinated Universal Time (UTC). Accessing Aurora Analytics To access Aurora Analytics, open your Account menu and click Analytics. Note: Members must have anAdmin or Analytics role to access Aurora Analytics From the Analytics page, you can access Dashboardand Reports. The Dashboardprovides you with an “at-a-glance” view of the activities that best indicate the overall health of your community and member engagement across your community. You can customize Dashboard settings to your requirements and get the most out of your data analysis. Reports present you with key metrics on content, boards, categories, and members in a tabular format. Related topics: Accessing Analytics Dashboard Dashboard Settings Aurora Analytics Metric Definitions Aurora Analytics Reports Refer to the Khoros Communities Analytics Essentials course for training on Communities Analytics.About Aurora Moderation
It is important for your community to be a positive space where members feel welcome, safe, and engaged. To foster this environment, moderators constantly monitor community activity by reviewing content for appropriateness, based on the guidelines you’ve put in place for your community. Using the Moderation tab in the Content Managementdashboard, moderators can quickly review and process large volumes of member-generated content. Depending on how you’ve set up your moderation process, content can be reviewed either before or after it is published to the community. From the Moderation tab, you can moderate forum discussion posts and their replies, ideas and their comments, as well as comments on blogs, knowledge bases, and events. Also, you can view the posts or private messages that are rejected as spam, abuse, or for other reasons and take further action on these posts or private messages. Moderation process You can set the moderation mode at the board level. Required: Moderators must moderate content to make it available in the community. (This was previously known as pre-moderation in Communities Classic.) Selective: The content is published, but moderators can moderate it after publication. (This was previously known as post-moderation in Communities Classic.) Auto-approved: Content does not require moderation and is approved automatically. Learn more about configuring moderation modes for various content types. When members post content on the community, the content is immediately routed to the Moderation, based on the moderation settings for that board. Note: When a board is set to Required moderation and members post content on this board, a confirmation message is displayed on the post indicating that post will be published as soon as it is approved from moderators: View Moderation tab Members with elevated permissions (Admins and Moderators) can access the Moderation tab in the Manage Content dashboard. Note that you must enable content moderation at the community level to view the Moderation tab. Members will see the Spam, Abuse, and Moderation tabs. The Moderation tab is where you can review content. By default, the Moderation tab is displayed with the list of unmoderated posts, where the Moderation status is set to unmoderated. The Moderation tab lists: Title: title of the post, reply, or comment Author: authors of the posts and replies Date: the date on which the post or reply is sent for moderation. Status: the publication status (Published or Unpublished) of the posts and replies. Number of views, likes, and comments for each post, reply, or comment. Note: You can sort this list based on the Date. From the Moderation tab, moderators evaluate the posts and replies. They can then approve or reject them, and also message authors about their content. When approved, posts are published in the community or remain in the community based on the moderation settings at board level. They are then removed from the Moderation tab. When rejected, the posts are removed from the community. The posts that are rejected as spam can also be viewed in the Spam tab. Learn more about approving or rejecting posts sent for moderation. To view the rejected posts or private messages, go to Filters and set Moderation Status as Rejected. From the Moderation tab, you can: Open any post to view the content Search and filter posts Approve or reject posts Message members on moderation actions about their posts Review the posts or private messages that have been rejected as Spam, Abuse, or other reasons Refer to the Khoros Communities Moderation Essentials course for training on this feature.Aurora: Bypass moderation
Members generally want to post content without moderation review. Admins can grant the Bypass moderationor Bypass comment moderation permissions to enable certain members to post or comment without moderation review. This option applies when the Moderation type is Selective or Required. Note: At this time, moderation cannot be set up by role, but this feature may be available in a future release. Instead, you can use theBypass moderationpermission to ensure that members with certain roles do not require moderation. See the screenshot below for the Discussion (forums) permission. This setting can be applied to all discussion styles. Learn more about configuring moderation modes for various content types.Aurora: Managing spam in your community
Managing spam in your community is integral part of keeping it safe and relevant for your members. The Manage ContentpageSpam management tab lists content that has been identified as spam. From this page, you can manage content marked as spam and take a variety of actions on this content. We recommend monitoring this page daily. To assist with effectively managing posts that have been marked as spam, we also recommend you selectHide from View for posts that have been reviewed and confirmed as spam. They can still be found by author or keywords in theFilters section of the Manage Content page. If you have been granted the appropriate permissions, you can access the Spam management page via Manage Content dashboard as shown here: The page lists: Title:titles of posts marked as spam Author:authors of posts marked as spam Date Rejected:the date on which posts were rejected as spam; you can sort the list based on thiscolumn Moderator:the member who reported the spam Note: Spam is removed from this view after 30 days, but you can still find it by searching. Manage spam On the Spam management tab, you can perform these actions: Review posts captured as spam Search and filter the content that are marked as spam Hide reviewed spam posts from the Spam management list. Tip: Hiding posts from the spam lists prevents you from re-evaluating them multiple times. You can still find these hidden posts if you search them in the Spam management tab. Recover a post mistakenly marked as spam Sort the spam posts in the ascending/descending order of post creation date by clickingDate Reportedin the column headerAbout Aurora Notifications
When you receive an in-app notification, a dot appears over theNotificationsbell icon in the header anywhere in the community. Click this icon to see a list of your notifications. You receive notifications for a variety of reasons around the community: New activity on content you follow (including Category, Board, Content, and Tag follows) Activity and updates on your content: Likes Solutions Mentions (Members and Content) Ranks Badges Related topics: Manage Follow and Notifications preferences for your account About Email NotificationsAurora: Configure SAML for the community
As an Aurora community admin, you can configure authentication for your community and integrate with your SAML IdP. To configure your SAML settings, go to Admin > Settings > System > Account. Learn more about Khoros SAML here. For more details regarding individual SAML settings, see About SAML settings. Set up basic SAML Configure your identity provider. Retrieve Community Service Provider Metadata XML: /t5/s/<communityID>/auth/saml/metadata If the SP metadata is inaccessible, contact Khoros Support and request that the SAML feature be enabled. Update the external Identity Provider configuration using values provided by Community SP metadata XML. Go toAdmin > Settings > System > Account. Scroll down to the SAML section, and below SAML Basics, ensure that Enable SSL Authentication is turned on if the SAML setup requires Secure-Sockets Layer (SSL) connection. In the IdP Metadata section, in the Metadata XML area, click Edit to paste your IdP metadata XML, provided by your IdP. In the Assertion to Profile Mapping section, enter the name of the attribute corresponding to the field you want to map from your SAML assertion (see Assertion to profile mapping in About SAML settings). A SAML assertion is the XML document that contains the user authorization details and is case sensitive. The identity provider sends this XML to the service provider. With the exception of the SSOID value, user settings can be gathered either directly from assertion attributes from your identity provider or else can be captured on the SSO User Registration form. Note: Adjustments to the SSO registration form currently require manual configuration by Khoros. When you have finished your SAML configuration and are ready to test, in the Single Sign On (SSO) section, turn on Use Khoros single sign-on (SSO). Set up SP-initiated SAML To set up SP-initiated SAML flow, you must also set up the basic SAML flow. Note: The Registration page, Sign-in page, and Sign-out page URLs (in the Single Sign On (SSO) section) must be preceded by your community ID. Contact Khoros Support and request the Community ID. Go to Admin > Settings > System > Account. In the Single Sign On (SSO) section, below SSO URLs, click Edit. In the Registration page field, enter the URL of the default page to which you want to redirect the users when they click the registration link to register to the community. If you use the (default) SAML POST binding for AuthN requests, then enter /t5/s/<communityID>/auth/saml/doauth/post If you use the SAML REDIRECT binding for AuthN requests, then enter /t5/s//<communityID>/auth/saml/doauth/redirect In the Sign-in page field, enter the URL of the default page to which you want to redirect members when they sign in to the community. If you use the (default) SAML POST binding for AuthN requests, enter /<communityID>/auth/saml/doauth/post If you use the SAML REDIRECT binding for AuthN requests, enter /<communityID>/auth/saml/doauth/redirect In the Sign-out page field, enter the URL of the default page to which you want to redirect members when they sign out of the community. Click Save. Turn on Use Khoros single sign-on (SSO). Set up IdP-initiated SAML To set up IdP-initiated SAML flow, you must also set up the basic SAML flow. If the SAML Request for community sign-in should originate from your Identity Provider rather than from the community itself, a slightly different configuration will be required. Go to Admin > Settings > System > Account. In the Single Sign On (SSO) section, below SSO URLs, click Edit. In the Registration page and Sign-in page fields, enter the URLs for your Identity Provider’s SAML sign-in/registration services. This is in contrast to SP-initiated configuration, which would specify community-specific SAML authentication services. In the Sign-out page field, enter the URL of the default page to which you want to redirect the members when they sign out of the community. Click Save. When you have finished your SAML configuration and are ready to test, in the Single Sign On (SSO) section, turn on Use Khoros single sign-on (SSO). Note: The query parameter that carries the community resource URL initially requested by the user when they sign in must be persisted with the SAML Response sent from your Identity Provider. This is to ensure the user lands on the community page where they signed in. This query parameter name is configurable using the Return Value Parameter Name setting. Ensure that the same parameter name used when the user is directed to your IdP is also sent with the SAML Response.
