Moderation Baselines and Queue
Standard or Strict classifier baselines, actions by source, and a queue with SLA timers, assignment, bulk actions, and appeals.
Moderation checks every post, comment, and video on your network against rules you chose, before anyone sees it. Clearly fine content is cleared. Only what needs a human call reaches your queue, within the SLA.
This capability arrives as a proposal when your network needs it, filled in from your brand context, and goes live when you confirm it. It's part of Controls, and Controls: roles, moderation, brand safety, and guidelines explains the baselines, actions, and signals moderation reads.
When to use it
Set it up before go-live, on every network. Some company playbooks start from the Strict baseline:
- Publishers and media companies: Strict moderation and a brand safety profile per brand. See Publishers and media companies: launch a publisher media network.
- Retailers: Strict moderation alongside the brand safety profile. See Retailers: maximize margin per impression on a retail media network.
- Community walls: set the baseline before the Community Wall Placement launches.
How it works
- Octo proposes the baseline, Standard or Strict, from your company type, audience, and model. Each baseline is editable by category.
- A classifier score, your keyword and topic blocklists, member reports, and partner flags all feed the decision.
- Flagged items are held, removed, or allowed with a label. You set the action per content source.
- The queue has SLA timers, assignment, bulk actions, and an appeal flow. Appeals land in the queue with the original decision attached, as Community Guidelines and Appeals describes.
- Member creators' posts reach the queue first, while Hosts and Contributors post straight to feed. Community Roles and Creator Tiers lists the tiers.
- Partner content can't bypass your moderation.
- Policies, legal constraints, and past incidents you add under Brand > Context > Policies shape the proposal.
Set it up
Octo proposes moderation with these steps already done. You review the result and confirm it.
- Pick a baseline under Controls > Moderation. Learn how in Set moderation, roles, and brand safety.
- Set the action for each source: hold, remove, or label.
- Assign a queue owner with the Content role. Business Account Roles and Scoped Roles covers the roles.
Choose Approve controls to start the queue and the weekly digest.
Settings
| Setting | What it controls |
|---|---|
| Baseline | Standard or Strict |
| Categories | What the baseline covers, editable one category at a time |
| Actions | Hold, remove, or allow with a label, per source |
| SLA | The timer on each item waiting for a decision |
Change them under Controls > Moderation. You can edit any line of the proposal before you approve it.
What it reports
The weekly digest summarizes the queue for you. Operations, ad ops & support: questions and answers explains how the queue and its SLAs run day to day.
- Queue volume: how many items wait for a human decision.
- Time to decision: how long items wait before someone decides.
- Appeal outcomes: how each appeal ended.
- Weekly digest: the week's queue activity in one summary.
Connect your systems
Moderation runs in Brand Control Center and needs no code. Two live pages cover the moderators and groups behind it. Add moderators to a community gives accounts the moderator role. Moderators approve join requests, review posts, manage groups, and add other moderators. Update a group and its members adds or removes members and changes a group's access settings.
The moderation calls in the Business Account API are proposed, not live. Live API today and the Business Account API roadmap maps what you can call now to what's planned.
