Moderation Console

The moderation console is built around a case-centric approach, consolidating all reports — from Proactive Detection or from user reports — on a given piece of content into a single view. This gives moderators a comprehensive summary of reports and the full context around each case. The interface is structured around four panels, with navigation and controls at the top.

On the top bar, you can see:

When you apply a policy, a decision or an action, Nima does not send it immediately. It holds the decision for 10 seconds and moves you to the next case. During those 10 seconds the UNDO button is live and cancels the decision entirely — nothing is enforced and nothing reaches your platform.

Once the 10 seconds elapse the decision is committed. From that point the only way to change it is ActionsActions, which undoes the enforcement rather than cancelling it.

This panel lists all the reports associated with the case, along with their audit trails. Each report card contains:

Reports can be filtered to help moderators focus on what they need most.

This panel shows the reported content and its details.

Content preview:

Content details / metadata:

When the reported item is a collection — an album, a listing with multiple images, a thread — the centre panel switches to a collection view. Every child item is listed with its own preview, and you can open each one individually while still deciding the case as a whole.

The third panel is about the account behind the content, so you can tell a first-time mistake from a repeat offender without leaving the case.

The panel is configurable per queue. T&S managers choose which attributes appear for each queue, so different teams surface the information relevant to their own review workflow.

Moderators can also reach out to the account owner through Request information, described below.

This is where you make your decision and apply the outcome.

You can choose only one policy or workflow action per report.

Both actions and policies displayed for each queue are configurable in QueuesQueues

Each policy, sub-policy and decision can carry a shortcut key, shown as a small chip on its button. Pressing the key applies that decision without reaching for the mouse — the single biggest difference in throughput between a new moderator and an experienced one. There is a separate shortcut for dismissing a case, and Esc closes the open list.

Shortcuts are set per user, so your team can standardise them or let each moderator choose their own.

Some policies are configured to trigger a report to an external agency. When you apply one of these, Nima asks you to confirm before the case is submitted onwards, so an external report is never filed without a moderator's explicit decision.

Opening a case locks it to you, so two moderators never review the same content in parallel. If you open a case someone else is already holding, Nima tells you who has it rather than letting you both work.

The lock is not indefinite:

Clicking the timer at the top releases the case deliberately, which is the clean way to step away.

Maximum handling time and the auto-release threshold are configured per queue — see QueuesQueues.

Once there are no cases left to serve, Nima tells you the queue is clear rather than leaving you on a blank screen.

When a case has already been processed, you can use ActionsActions to change the previously applied decision. This is useful for correcting mistakes identified during quality control or when new information changes the original decision.

To revert an action:

When you apply a revert action:

Revert actions are configured in Configure > Trust & Safety > Actions as any other action.

If the webhook carrying your decision to your platform comes back with an error, an Action Failure Details entry appears on the case. It opens the response Nima received, so you can tell the difference between a decision that was never applied and one that simply hasn't propagated yet.

Cases in this state are also highlighted in the Reports List, and can be filtered with the Failed Reports status.

To protect moderator wellbeing, you can blur sensitive images. Click the unblur button next to any blurred image to view the original, or click blur to reapply the effect.

Blur and greyscale intensity are set per queue, so a team working sensitive content can have a stronger default than a team working spam — see Blur FunctionalityBlur Functionality.

When reviewing text in other languages, use the built-in translation feature. Select your target language from the dropdown and click translate to instantly view the content in that language.

Nima can also automatically translate content into English inside the console — including report text, reason-for-appeal messages, in-console text content, and audio transcripts — so moderators can review multilingual content without switching to an external translation tool. This is available on a per-contract basis.

Click the policy guidelines icon in the console to open a right-side drawer listing all your platform's policies and their descriptions. Moderators can reference policy details without navigating away from the current case, reducing context-switching during active moderation.

Two further drawers can be enabled on your instance:

Escalate and Re-Route sit at the bottom of the right-hand panel.

For complex or sensitive cases that need expert review, click Escalate. Select the appropriate escalation queue from the dropdown and confirm to move the case. The case is immediately removed from your queue and sent to the specialized team. Escalation queues are created in QueuesQueues. Cases can be escalated also from the List View.

Escalate is only offered on cases that have not yet been actioned, and reads "Already Escalated" when the case is in an escalation queue already.

When a case is better suited to a different workflow or team, you can Re-Route it instead of escalating. Use it to send the case to another queue (for example, a different language, country, or product queue). Once re-routed, the case leaves your queue and appears in the destination queue's backlog. Re-Route stays available after a case has been actioned.

When you need more context before making a decision, use the Request Information feature to contact the reported accounts or reporters directly.

How it works:

Moderators are notified whenever a new answer is submitted to one of their information requests.

To customise the email templates of your RFI, reach out to the Tremau Team.

Moderators can add notes to a case to share context and reasoning with the rest of the team.

Notes are scoped to the content, not the individual report, so a note added on one report is visible across every report about the same content — giving teams a single, consistent thread and avoiding duplicated effort when the same content is reported multiple times.

Nima includes an in-app notification center that alerts moderators when they are @mentioned in case notes. A badge shows unread alerts, and each notification links directly to the relevant case so moderators can respond without losing context. Notifications can be marked as read or unread, deleted, and managed individually or in bulk.

A case can be exported as a PDF audit trail, capturing the content, the reports against it and the full history of decisions — useful for legal requests, regulator correspondence and internal review.