Set up Nima
Rule Configuration
5 min
rules are the mechanisms that parse content entering nima and distribute it for moderation, either through automated enforcement or by routing it to human moderators types of rules nima supports two main types of rules, configurable in the rule engine proactive detection rules to automatically ingest and analyze any type of content uploaded with ai models and triage it based on the thresholds (confidence levels) you set to automatically enforce policy violations for high confidence cases π΄ send content to the configured human moderation queues for cases flagged as π dismiss content flagged as π’ if no issues detected queue routing rules (only for human moderation) to parse content coming from sources other than proactive detection (user reports, user report illegal content, lea or trusted flagger notices) into queues for manual review, where moderators apply policies configuring rules proactive detection rules a proactive detection rule is associated to one of your docid\ o4mxk fvhcwa88dmpctva and displayed on the same screen as each policy steps to configure source is pre selected to proactive detection select other trigger criteria choose additional conditions such as content type (mandatory), label , custom attributes , and all the available variables set up ai detection by selecting the provider and the model(s) to utilise for multiple models, users can use the and / or operator after this, users can select the different thresholds for detection, resulting in π’ for cases to dismiss π for cases to send to queues π΄ for cases where the selected policy will be automatically enforced assign policy choose which policy/sub policy applies for π΄ cases (pre filled if set from the policies screen) assign queue for cases that will be selected as π itβs possible to configure fewer than three threshold zones by overlapping the sliders depending on your goals, you can use only π’ and π dismiss non issues or send flagged content to queues π’ and π΄ dismiss non issues or automatically enforce policy π and π΄ route all flagged content either to queues or automatic enforcement queue routing rules queue routing rules are associated to one of your docid\ azsiick6eehflzwytql v and displayed on the same screen steps to configure select the channel among the different options, including user report, user report illegal content, lea, trusted flaggers select other trigger criteria choose additional conditions such as content type , label , custom attributes , and all the available variables assign the queue to which the content matching the criteria will be redirected in case you want to pre assign policies > enable the toggle "automatically apply policy or workflow action" to automatically apply a policy on intake how to prioritise rules in nima as multiple rules can have the exact same criteria, nima allows users to choose how they are prioritised in the rules tab, by simply dragging and dropping the different rules by ranking rules, you are setting what rules with same criteria are hit first by content entering nima from the same page, users can also create new rules and edit pre existing rules finally, the rules tab is where users can get a full overview of how automated rules have been mapped to policies