ContributionsMost RecentMost LikesSolutionsAbout 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. 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. 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 header Flood controls for Aurora communities With Khoros, there are limits on how often people are allowed to post, upload images, videos, and attachments, tag content, send private messages, and other community actions before triggering flood controls. Flood controls are in place to help combat potential spam. Note: Those with the Administrator and Moderator role are exempt from flood control restrictions; these thresholds affect only regular members. The following table lists the default flood rate settings for various actions performed by the member within a specified period of time. Actions Flood Controls Post content A member can't post more than: 3 posts in 30 seconds 15 posts in 10 minutes 50 posts in an hour Send Private Messages A member can't send more than: 1 private message in 30 seconds 5 private messages in 10 minutes 20 private messages in an hour Upload Images A member can't upload more than: 100 images at a time 1000 images per day 1000 images in the community Upload Videos A member can’t upload more than 50 videos per day in the community. Upload Attachments Members can’t upload more than 100 attachments per post per day. Like content A member can't give more than: 50 likes per minute 500 likes per hour 5000 likes per day Tag content A member can’t add more than: 20 tags per minute 500 tags per hour 5000 tags per day Mention people A member can’t mention more than 10 members in a single post. To configure these flood controls, contact the Support team. Aurora: Confirm reported posts as abuse After reviewing the reported posts or replies, Moderators can confirm the posts or replies as abusive content. After you confirm the abuse, the posts are removed from the community. Aurora: Set forum permissions In the community, you can set forum-specific permissions to control who can read, start, reply to, and manage discussions. Aurora: Enable content moderation and set content moderation defaults Community moderators review and process large volumes of member-generated content. Moderation is an important part of keeping a community a safe and engaging space for your members to participate. When Content moderation is enabled (from the Settings > Features > Moderation area), members with appropriate permissions can review content from the Content Managementdashboard. Depending on how you configure the moderation settings, content can also be auto-approved and skip the moderation process. The moderation process depends on the defaults you set for various boards. Admins can set these moderation defaults for forum discussions and replies, blog comments, ideas and their comments, and knowledge base comments at the community, category, and board levels. Auto-approved:The content is auto-approved and made public without going through moderation review unless flagged. Recommended for trusted areas that are self-regulated by a small group of members. Selective: The content is made public to the community without going through moderation. However, moderators can selectively review this content later, and based on the review, the content stays or is removed from the community. Required:The content must go through moderation for review, and based on the moderator's evaluation, the content is either published or removed from the community. By default, Selective moderationis set for all boards. Understanding the different moderation options Before configuring the content moderation defaults, you must understand the benefits and risks of each option: Auto-approved: Set Auto-approved for places that are designed for open discussions without any need for regulating the content posted by members. Use this option in places that are self-regulated by a small group of members who are accountable for their actions. However, we still recommend you implement the moderation process within the community to avoid spreading inappropriate information. Selective: Similar to Auto-approved, the Selective moderation process also encourages open communication among members in that they can publish content immediately without prior review. Moderators can still review the published content to ensure the posted content is appropriate and adheres to the community’s principles. Use this option in places where members expect fast-paced and live interaction without having to wait long for the moderation process to complete. However, when moderation is delayed, there is the potential risk of inappropriate content (abuse or spam) being posted that impacts readers and disrupts the community. Compared to the Required moderation process, this process is less effective in avoiding spam and abusive content. Required: Required moderation is the best way to combat spam and abusive content because the content is sent to the moderation before it’s made public in the community. This also protects your community’s reputation and creates a safe space for your members by ensuring the appropriate content is posted in the community. However, this process relies on additional resources to review the content, which may delay making the content public. This can disappoint members who want their content to be made public quickly. Enable and set content moderation defaults at community level Sign in to the community as an Admin. Open the Account menu and go to Settings > Features. Click Moderation. The General settings page displays spam and content moderation settings. Here, you can set default moderation statuses for forum topics and replies, blog comments, event comments, idea and comments, and knowledge base comments. To enable content moderation, toggle on theContent moderation option. Note that you cannot moderate the content across the community if this option is not enabled. Under Content moderation defaults, set default moderation statuses for forum topics and replies, blog comments, event comments, ideas and comments, and knowledge base comments at community level. Let’s look at an example in which you want to moderate all forum topics and their replies in the community before they are published to the community. To enable this moderation workflow, set the Default Forum topic and reply status as Required moderation. Based on these settings, all forum topics and replies are sent to the Moderationfor review and are published after the moderator’s evaluation. Similarly, you can set default statuses for other content types. Set content moderation defaults at category, group, or board levels The Content moderation defaults set at the community level are inherited to the category, group, and board levels. You can override these options at various levels as needed. Based on the inheritance, the settings applied at different levels are inherited to child places from their parent levels. For example, the content moderation defaults set at category or group levels are inherited to their child places. Learn more about setting inheritance. Let’s look at an example in which you want to set content moderation defaults at category level. To set content moderation defaults at category level: Open the Account menu and go to Settings > Community Structure. On theCommunity Structure page,click the category where you want to set the content moderation defaults. In the category settings, go to the Moderation section and set Content Moderation defaults as required. When you’ve adjusted a setting for a child place, a PARENT OVERRIDE indicator is displayed next to that setting for the child place to indicate that it overrides the settings of its parent. Similarly, you can set content moderation defaults at the group and board levels. Based on these board-level settings, when members post content on the community, the content is immediately routed to the Moderation for review. 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: From the Moderation tab, moderators can review content for appropriateness. They can then approve or reject it, and also message authors of the posts. Learn more about moderating content. Note: it is not possible to set different moderation levels for comments(or replies) and main posts Grant permissions to moderate content Moderation permissions should be granted only to roles assigned to trusted individuals. To manage this permission: Navigate toAdmin > Settings > Users > Roles and Permissions. In the row of the role for which you want to manage this permission, click theOptionsmenu and thenEdit. In thePermissionsarea, belowModeration, locateModerate Content. SelectGrantorDenyas required. Aurora: Delete a group and sub-groups Group Owners and Community Administrators can delete groups. Warning: Deleting a group permanently deletes all of the content, membership, and settings associated with the group. The action cannot be undone. No notification is sent when a group is deleted. Delete a group in Community UI Delete a group in Community Admin Delete a group in Community UI Sign in to the community and navigate to the Group 9age for the group you want to delete. From the Options menu, click Edit Info. In the Edit Grouppage, go to the bottom left of the page and click Delete Group. Click Delete Groupin the confirmation modal. The group is deleted and you are returned to the group parent page (the top-level Community page or the parent Category page). Delete a group in Community Admin Go to Community Admin > Community Structure. Navigate to the group you want to delete. Hover your cursor over the group and select Delete. Click Delete Place to confirm. The group is deleted. Note: You cannot delete the boards with in a sub-group. Aurora: Configure Registration and Sign-In settings The Account & Privacy page contains settings related to registration, sign-in, and sign-out. This article covers registration and sign-in settings. To learn about configuring SSO options, seeConfigure SSO settings for the community. Registration settings All anonymous users must register to participate in the community. To register, they must enter mandatory fields such as Username, Password, and so on. By default, the Registration window includes these fields: Admins and members with appropriate permissions can enable or disable these registration fields from the Settings page as needed. To edit registration settings: Sign in to the community as an Admin. Open the Account menu and click Settings. Go to System > Account & Privacy. Go to the Registration section and turn on/off these options: Enable member registration: Turns on or off the community member self-registration flow. By default, this option is enabled. This option is turned off for private and invite-only communities, where anonymous users are not allowed to register in the community. Add date of birth field to registration page: Controls whether the Date of Birth field appears on the Register window. Use Date of Birth to enforce the minimum age requirement: Toggle on this option to validate the date of birth provided by the user against the minimum age required for registration. Require users to confirm that they meet the minimum age requirement: Toggle on this option to add a field on the Registration window for the users to confirm whether they meet the minimum age required for registration. Set the Minimum age required for registration. As per the Children’s Online Privacy Protection (COPPA) rule, users must be at least 13 years old to register to the community. Auto-assign role upon registration: If you want to automatically assign a role to a new member when they register, click Edit by this option. In the field on the window, enter the role you want new members to be assigned. Terms of service acceptance required: Toggle on this option to add a field on the Registration window for the users to read and accept the Terms of Service (TOS). You can turn off this option if Single Sign-On (SSO) is used and you already have TOS acceptance as a requirement in the SSO configuration. Also, Admins can View/Edit Terms of Service in the required language. Learn more about editing the Terms of Service for the community. When all the options are turned on, the Register window looks like this: Sign-in Settings To edit sign-in settings: Sign in to the community as an Admin. Open the Account menu and click Settings. Go to System > Account & Privacy. Go to the Sign in section and turn on or off the Keep me signed in setting. When you turn on this setting, the Sign In window has the Keep me signed in checkbox selected by default for the member signing in. About the Salesforce and Aurora integration The "Khoros Connector for Salesforce" enables you to create a tight integration between your Khoros Community Aurora content, Salesforce content, and Salesforce cases. For more information on setting up this integration, contact Khoros Services. Note: You must have a full Salesforce license to take advantage of the Khoros/Salesforce integration. The following are the key features of the Aurora and Salesforce integration: Automatically escalateunanswered threads toSalesforcecases Manually escalate threadstoSalesforce cases Provide a private support case portal to their community members View community member details and statistics within Salesforce Use enhancedfederated searchacross Aurora and Salesforce content Link Salesforce and Khoros Community Aurora content viapostbackfrom Salesforce to the community Before you start Decide on your target Salesforce environment. Khoros strongly recommends that you first enable the integration in a Salesforce developer or sandbox org before deploying the integration to your production environment. Make sure you have your Salesforce integration enabled in the Aurora community environment that will connect to your Salesforce environment. Your Khoros Customer Success Manager can assist with this process. Khoros will enable the integration in your staging environment before enabling it in your production environment. Learn more about Installing and configuring your Khoros/Salesforce.com v3/v4 integration.