Settings

Introduction

Admins have a choice of 3 options to set up moderation for their domain. These include:

  1. Moderate only flagged content.

  2. Moderate comments, posts, questions and updates.

  3. Moderate comment posts, questions and updates on which content the following words.

By default, “Moderate only flagged content” is selected.

Exceptions

  • Team admins in their team (this is the default option): When you select this option, content posted by team admins in their teams will not be added to the moderation queue.

  • Specific users: Select lists of users whose posted content will not go into the moderation queue and does not require approval or rejection.

  • Specific team: Select lists of teams whose posted content will not go into the moderation queue and does not require approval or rejection.

The exception section is available only when option 2 or 3 is selected.

All content posted by Domain and Intranet admins are always exempted from moderation.

Option 1: Moderate content that is flagged by users

  1. In this option, the content when posted is available & visible to the community or user portal in real time.

  2. Any user can use the "Flag" action to add it to the moderation queue for review.

  3. Moderator has the permission to view any content that is present in moderation queue and edit it.

  4. Moderators can approve or decline the request.

Option 2: Moderate comment, posts, questions, and updates

  1. In this option, all comments, replies, updates, questions and posts when posted are not available and visible to the community or user portal in real time.

  2. They are available and visible to domain & moderation admins only to approve or decline in the moderation queue (admin portal).

  3. When approved:

    • User posted content is available on the community / user portal and notifications are pushed out.

    • The moderation queue request moves to the approved status in the queue.

  4. When declined:

    • User posted content does not become available in the community / user portal.

    • The moderation queue request moves to the declined status in the queue.

  5. In this option, once the content is approved, the user can’t edit the content (they can still delete it).

Option 3: Moderate all comments, replies, updates and questions that have one or more of the keywords that are configured.

  1. In this option, all comments, replies, updates, questions and posts when created will be checked if they match one of the keywords.

    • If a match is found, the content will not be available & visible to the community / user portal in real time.

    • If a match is not found, then the content will be available & visible to the community / user portal in real time. Notifications to users will be pushed out.

  2. If the content ends up in the moderation queue, the remaining processing on approval or decline is the same as option 2.

  3. In this option, once the content is approved, the user can’t edit the content (they can still delete it).

In the moderation queue, a request will stay for a maximum of 60 days and after that the request is automatically removed.

  • If the request is in declined state at the end of 60 days, then in addition to the request entry in queue. The content associated with it is also permanently deleted.

  • If the request is neither accepted nor declined at the end of 60 days, then in addition to the request entry in queue. The content associated with it is also deleted (will be available in trash can until the trash can limit expires).

To get a list of potentially offensive words, research lists of inappropriate words on popular websites like GitHub or GitLab. There, you might find community-contributed lists you can use for your purpose. Here is an example of one such list: https://github.com/LDNOOBW/List-of-Dirty-Naughty-Obscene-and-Otherwise-Bad-Words

Moderation Notifications

  • The moderation module has notifications for both domain/moderation admins and the person who posted the content, keeping everyone in the loop.

  • Domain and moderation admins are notified when new content is submitted for moderation.

  • The user who posted the content is notified when their content is approved or declined.

User Pending Items

  • When the user posted content is pending (or rejected) in the moderation queue, the author of the content can see the items in their profile under ‘Pending Items’.

  • This tab will be empty if no content of the user is in the moderation queue (in pending or rejected state).

  • A user can’t see this tab for other users. They can only see it on their own profile.

Last updated
https://guides.mangoapps.com/admin-guide/moderation/settings
guides.mangoapps.com
CC-MAIN-2024-22
626515
application/http; msgtype=response
sha1:C4LEWIDI3ETIEGCMT2NS44XGNLWTTWVY
<urn:uuid:38bae7f0-a507-4f62-829e-1a133a64783b>
2024-05-24T20:17:49Z
104.18.40.47
text/html
sha1:APXASA672ZL757HC5Y4QO3UKNAORUYBN
<urn:uuid:4b3e3630-5059-40de-9aa1-11f7db9cfff1>
https://guides.mangoapps.com/admin-guide/moderation/settings
response
<urn:uuid:235053ce-ef6e-4fee-803a-62fa3cc907ef>
isPartOf: CC-MAIN-2024-22
publisher: Common Crawl
description: Wide crawl of the web for May 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-217
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/