Visualising a case in Nima

the queues page when you log in as a moderator, you land on the queues page, listing every queue you're assigned to team assignments to queues are managed in queues docid\ azsiick6eehflzwytql v settings, so you only ever see the queues your teams are responsible for — administrators see all of them the page has 2 tabs , both organised by queue reports reports waiting to be reviewed by moderators for the first time appeals docid\ hadsvd38gpyc7canb4oyi reports that users have appealed after the first review, pending moderators second review each tab shows the total pending across all your queues next to its name, and the page shows when it was last updated it refreshes automatically every 5 minutes pending caseload and sla tracking on the reports tab, every queue is one row with three numbers that together tell you where to start total pending cases — how many cases are waiting in that queue this is counted per case, not per report when several people report the same piece of content, you review it once, so it counts once here in sla breach — how many of those pending cases have at least one report that has been waiting longer than the queue's sla it uses the same case level unit, so it can never be higher than total pending cases when nothing is overdue the number sits in a neutral grey badge; as soon as a case breaches, the badge turns red — the fastest signal on the page sla — the handling time target configured for that queue (for example 24h , or 1h 30m for fast turnaround queues) a queue with no sla configured shows and will never show a breach, however long its cases wait very large numbers are shortened to 1000+ queues are listed with the busiest first, and the review queue — where cases that need a second look after external reporting are held — sits at the top when your platform uses it escalation queues are marked as such next to their name queues with nothing waiting are moved out of the main list into a collapsible empty queues section at the bottom, with the count of how many there are, so the list you see stays focused on queues that actually need attention those rows still show the sla target nima remembers whether you left the section open or closed from each row you can start working straight away — see queue viewing modes below the appeals tab counts differently appeals are handled individually rather than grouped by content, so it shows total pending appeals and how many have been waiting more than 24 hours if a queue's sla is changed in settings, both the target and the breach count follow from the next refresh onward — breaches are always recalculated against the sla currently configured, never frozen at the time a report arrived the condensed queue side view now surfaces only the in sla breach figure, keeping the at a glance view focused on the queues that need attention most team leads with access to overview see the same queue health data there, alongside which moderators are currently available queue viewing modes once you open a queue you can work it in three different ways , each suited to a different task 1\ list view displays cases in a table, one row each it works well for manual triage and for actioning several cases at once cases appear as rows that are easy to scan select several rows to apply a policy or decision, escalate, or re route them together customise which columns appear handle specific cases out of the normal order when needed list and grid view show only the 10 most urgent cases in the queue , in prioritisation order — not the whole backlog as you process cases, new ones take their place to search or filter across every report, use the reports list instead 2\ grid view shows the same 10 cases as cards instead of rows, four to a line it suits visual content, where seeing the media matters more than the metadata switch between the two with the list / grid toggle above the table cases appear as cards with the content preview foremost which fields appear on a card is configurable, in the same place as list columns 3\ moderation console docid\ angnoc xkytjfghpyhxmz shows cases one at a time when you click the play button, using a case centric approach that consolidates all reports on a given piece of content into a single view it provides a full screen view with comprehensive context for each case, so nothing gets overlooked this mode is ideal for working through a queue quickly and sequentially cases appear in a continuous sequence, moving automatically to the next case after you make a decision each case view includes a summary of all reports, a customisable reported account section, and the full audit trail streamlined workflow keeps you focused on making decisions without having to select each case manually see moderation console docid\ angnoc xkytjfghpyhxmz for a detailed walkthrough of the interface customising what you see all three modes are configured from the same customize drawer, opened from the list or grid view it has a tab per mode — console, list view, grid view — so you choose which fields appear where, and drag them into the order you want these settings apply to the queue, not just to you everyone working that queue sees the fields you choose, and nima records who last changed them agree the layout with your team before rearranging a shared queue the same drawer holds the blur and greyscale intensity for the queue — see blur functionality docid\ aa7jy1u8cvlirssikv i which custom attributes are available to choose from is set per queue by t\&s managers in queues docid\ azsiick6eehflzwytql v settings, so different teams only ever see the information relevant to their role — the data minimisation principle applied to moderation your choice of list or grid is not remembered between visits each queue opens in list view how cases appear and are ordered which cases appear in which queues depends on the rules you've configured by default, the order of cases within each queue is based on their severity nima puts the most critical content first, so you can address urgent issues quickly you can change that order to match your platform's needs — see prioritisation engine docid\ jqgkzzngeonnuj8xbsibw