How does automation work?


Automation rules have an associated action which the rule's conditions are satisfied. Those actions :

  • Approve instructs Implio to approve the item
  • Refuse: instructs Implio to refuse the item
  • Send to manual queue: instructs Implio to send the item to a specific queue for manual review.
  • No action: instructs Implio to not perform an action, but still log the fact that the item matched the rule. This is useful for fine-tuning your rule, or simply to get a better understanding of incoming content.

But what happens when several automation rules have matched an item, each with a different action (Approve, Refuse, Send to manual queue)? This is where the orchestration comes into play. 

The orchestration turns a set of rule actions into a single moderation decision. It governs the priority of one action over another, and determines what happens when no automation rule with an actual action has matched.

Default orchestration

This section describes the default orchestration for any new Implio team. We have found this orchestration to be the best-suited for most use cases.

The following diagram illustrates the priority between the different possible actions:

  1. Approve actions has the highest priority. This allows you to have whitelisting rules that will approve content no matter what.

  2. Refuse actions come next. Any Refuse rule will have priority over Send to manual ones.

  3. In the absence of an Approve and Manual action, any rule matched with a Send to manual action will trigger a manual review.

  4. Approve being the default action, an item will be approved if no rule with a Refuse or Manual matched.

Was this article helpful?

Can’t find what you’re looking for?

We are here to help! Click that big button or chat bubble to get in touch with our support team ➡