Skip to main content

Setting Up Your Moderation Views – Workflow

Once data flows to Alice, you can define different Moderation Views and action buttons for different teams and/or moderators. These are fully customizable based on your organization’s needs. They provide an easy way to prioritize and make your teams more efficient. Moderation Views are fully customizable and are most commonly based on Violation Categories, languages, or an item's status. A default Moderation View is provided that includes all items. You can create as many Moderation Views as you want.

Here are two examples of a workflow that sets up a Moderation View in the T&S platform. Please note that these are just examples. You can build a Moderation View based on any filtering rule derived from the data, and choose any data points to appear in the Moderation View.

Note – It is not mandatory to set up the Moderation Views in this order because you can create, modify and delete the definitions of your Moderation Views and the T&S platform at any time.

Setting Up a View by Violation Type​

Here is a suggested workflow for setting up multiple Moderation Views, each of which handles different types of items according to the type of violation that Alice detected in them.

To set up your Moderation Views by Violation Type –

  1. View Configuration – Define a Moderation View for each type of violation by defining a filter that routes items with this violation to this Moderation View. See View Configuration for more information.

  2. Define Webhooks – Plan the type of actions that a moderator might trigger in each Moderation View in order to affect something outside of the T&S platform (such as to remove an item or block a user on your platform) or on a third-party application (such as to create a ticket in Zendesk). Make sure an integrator or a programmer has defined the relevant Action Webhooks, as described in Action Webhooks. Make sure that a relevant API is defined on your platform or on the third-party app to execute the action upon receiving the Action Webhook from the Alice T&S platform.

  3. Define Actions – Define actions in the T&S platform that can be triggered by a moderator when they click a button in a Moderation View. These actions can change the status of an item, change an item’s properties or trigger an Action Webhook that affects your platform or third-party application (as described above). See Action Management for more information.

  4. Define Moderator Buttons – Define which action buttons will be available for moderators to click in each Moderation View. See Action Mapping for more information.

  5. Test – Make sure that items are arriving from your platform at the T&S platform (via API or file upload) as described in the Alice Integration and API Guide and then try out the Moderation Views, as described in the Alice T&S Moderation Guide – Coming Soon.

Internal Review Flow – Setting Up a View by Item Status​

The T&S platform enables you to assign each item a status. The status of an item can be changed by a moderator clicking a button while reviewing that item or by an Automated Workflow based on the properties of that item. These status changes enable a kind of state machine that transitions an item through various states. For example, an item might transition through the following Moderation Views, according to their statuses – Suspected, Pending Review, Enforced and Dismissed.

The following is a suggested workflow for setting up multiple Moderation Views, each of which handles items with a different status. This workflow defines that items appear in the relevant Moderation View, when their status is changed.

To set up your Moderation Views by item status –

  1. Define Webhooks – Plan the type of actions that a moderator might trigger in each Moderation View in order to affect something outside of the T&S platform (such as to remove an item or block a user on your platform) or on a third-party application (such as to create a ticket in Zendesk). Make sure an integrator or a programmer has defined the relevant Action Webhooks, as described in Action Webhooks. Make sure that a relevant API is defined on your platform or on the third-party platform that will execute the action upon receiving the action webhook from the Alice T&S platform.

  2. Define Actions – Define actions in the T&S platform that can be triggered by a moderator when they click a button in a Moderation View. These actions can change the status of an item and trigger an Action Webhook that affects your platform or third-party application. See Action Management for more information.

  3. Define Moderator Buttons – Each action changes the status of an item. Define which action buttons will be available for moderators to click in each Moderation View. See Action Mapping for more information.

  4. View Configuration – Define a Moderation View for each item status by defining a filter that routes items with this status to this Moderation View. See View Configuration _Setting_Up_Moderation for more information.

  5. Test – Make sure that items are arriving from your platform at the T&S platform (via Api or file upload) as described in the Alice Integration and API Guide and then try out the Moderation Views, as described in the Alice T&S Moderation Guide – Coming Soon.