Setting up Nima

nima is configured in a specific order, because each piece depends on the one before it a rule cannot route to a queue that does not exist, and a policy cannot be saved without an action or a tier to enforce it working through the steps below in sequence avoids most of the dead ends everything here lives under configure in the left hand navigation 1\ policies start here policies are the spine of nima — every case is assessed against them, and rules, queues and enforcement all reference them define your policies and sub policies, and map each one to the outcome it should trigger see policy configuration docid\ r6vgf6m3d k8slkyopppp 2\ actions a policy cannot be saved without an enforcement outcome, so create your actions early actions are also what connect nima to your platform each one calls a webhook that carries out the enforcement on your side see actions docid\ lsfkyoqsi365x alowit1 3\ queues queues are where cases wait for human review create them before you build routing rules, since a rule has to point at a queue that already exists decide which teams work each queue, which policies they can select, and what sla applies see queues docid\ azsiick6eehflzwytql v 4\ rules with policies, actions and queues in place, you can define how content flows proactive detection rules that analyse content with ai, and queue routing rules that direct reports from users, trusted flaggers and law enforcement to the right place see rule configuration docid\ hfx29ae9o5ktdj2 dokxb 5\ account strike system optional, and best added once your policies are stable the strike system escalates enforcement as an account accumulates violations, rather than applying the same action every time see account strike system docid\ imksiysjewzvi5ne93o7n 6\ abuse detection optional penalises accounts that repeatedly submit reports which turn out to be unfounded, protecting moderator time on platforms with open reporting 7\ test before you go live use test rules on the rules page to submit sample content and confirm your configuration behaves as intended — which rule matches, which provider runs, and what outcome results — without touching live traffic steps 1 to 4 are the minimum needed to process content steps 5 and 6 can be added at any point afterwards