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 headerAbout Aurora Abuse management
Even though we'd like to believe that everyone in our community is there for the greater good, helping people out and offering (albeit sometimes strong) opinions, we know that there are members who are just up to no good. For these, and for all the other rule-breakers—intentional and otherwise—you need a way to handle posts that fall outside of your community guidelines and the people who post them.About Abuse Notifications
Admins and moderators can specify designated email addresses for receiving abuse reports related to posts, members, or private messages. This ensures that reports are promptly directed to the appropriate members, facilitating timely decisions and actions to maintain community standards and safety. To set the email addresses, Go to Settings > Features > Moderation > Abuse Notification. Select Edit. A window appears on which you can enter the email addresses where abuse reports on Posts, Private Messages and Members can be sent to. Here’s an example of an email received for a post that was reported for abuse. Note: While at the community level you can specify email addresses for receiving abuse reports on posts, private messages, and members, at the category level, you can set them to receive reports only for posts. Below is an example of the abuse notification settings at a board level. Related Topics Abuse managementAbout Aurora Communities spam management
Khoros Community spam management tools run in the background, where each new message is logged and tested for spam. Additionally, our system learns about your site content as it monitors all your boards and forums, enabling it to improve its content filtering over time.Aurora: Review posts captured as spam
You should periodically review the posts that are flagged as spam and captured in the Spam management tab. Each community site is unique, and the best way to help the automated spam filter to learn more about the content on your site is to review the captured posts (especially in the first months) and recover any posts mistakenly marked as spam. Note: The Spam management tab includes data for only the last 30 days. To view posts captured in the Spam tab: Sign in to your community as an Admin or Moderator. Open the Account menu and click Manage > Spam. The Spam tab is displayed. Click the Title of any post to review the content. The title of the post and other options are displayed to manage the spam. Actions you can take include: Navigate to the post to view the content Hide the post from the Spam management view Mark the post as not spam if the post is mistakenly marked as spam Related topics: Search for specific content in the Spam Management page Mark individual posts as spamAurora: Hide reviewed spam posts
On the Spam management tab, you can hide the spam posts that you have already reviewed so that you or other moderators do not re-evaluate them. To hide a post: Sign in to the community as an Admin or Moderator. Open the Account menu and then click Manage > Spam. On the Spam tab, you can hide a post from view in several ways: Open theOptions menu and clickMark as Not Spam. Click the Title of the post to review the post and Hide from View. Click Hide. The post is hidden from the Spam management view, but you can search for the post using the Filter options available on the page: Learn more about searching for content in Spam management.
