Queues

queues are lists where cases wait for review by human moderators and are the backbone of nima’s human moderation workflow as described in docid\ hfx29ae9o5ktdj2 dokxb , cases can be sent to queues by either docid\ hfx29ae9o5ktdj2 dokxb – when content is flagged as 🟠 and requires human review after ai detection, or docid\ hfx29ae9o5ktdj2 dokxb – when content is directly routed for manual review (e g , user reports, lea requests, trusted flagger notices) all the rules routing cases to a queue are displayed on the left hand side of the page additionally, each queue page displays which teams can access it and what policies and workflow actions are available how to create and set up a queue team leads or administrators can create queues in settings > queues add new queue – start by creating a queue queue name – choose a clear, descriptive name (e g , harassment reports eu ) sla configuration – define the maximum handling time (in hours) to set a service level agreement (sla) for timely moderation assign moderator teams – select which teams are responsible for this queue; moderators of assigned teams will have access to queues in their dashboard assign policies – limit or focus the policies available in this queue to ensure precision in decision making assign workflow actions – define what moderators can do in this queue, e g no policy violation, approve content , when deleting a queue that has rules assigned to it, bulk reassign all associated rules to another queue directly in the deletion flow select the target queue from the dropdown and all rules will be transferred automatically you will also be prompted to select a queue for transferring any existing cases escalation queues the same process applies to escalation queues, which are specialised queues for handling high risk or complex cases these queues are typically reserved for senior moderators or specialist teams they ensure that elevated risks (e g , threats of violence, child safety) receive additional scrutiny before action is taken