Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Administration & Settings

Admins manage the organization’s configuration including settings as well as specific configuration for items, actions, policies, user access, and integrations from the Settings menu.

Settings

Configure the organization profile and org-wide behavior including single sign-on, appeals, review console, wellness, and more under Settings. Many of the toggleable features are off by default, so opt in to the ones applicable to your platform and team.

Organization

Identity and contact information for your Coop organization.

Settings dashboard showing the Organization tab with fields for organization name, email, website URL, and on-call alert email

The On-Call Alert Email requires an email service to be integrated with your Coop deployment. Coop supports email service integration but does not ship with one configured.

Single Sign-on

Enable SAML-based SSO so users authenticate through your identity provider instead of email and password. Coop supports any SAML 2.0 identity provider. See single sign-on in the deployment guide for an example of setup using Okta.

SSO tab in Settings, showing the SAML/SSO enable toggle and fields for SSO URL and SAML Certificate

Appeals

Enable user user appeals of decisions made in Coop, and configure your platform’s appeals callback URL, headers, and body.

Appeals tab in Settings showing toggle to enable appeals, callback URL, headers, and body fields

Review Console

Behavior of the Review Console for reviewers in your org. Configure moderator requirements, queue management behavior, and webhooks.

Review Console tab in Settings with toggles for Require Policy, Require Decision Reason, Hide Skip Button, Enable Preview Jobs View, plus an Ignore Callback URL field

Wellness

Reviewer wellness controls for media displayed in the Review Console including blur, grayscale, and mute. These help reduce exposure to harmful media during review.

Wellness tab in Settings with Blur Media slider, Greyscale toggle, and Mute Videos toggle

Other

Settings that don’t fit cleanly into the other tabs including configuration for the Partial Items endpoint and the ability for job decisions to reference multiple policies.

Other tab in Settings with fields for Partial Items Endpoint, Partial Items Request Headers, plus toggles for Reporting Rules, Multiple Policies Per Action, and a User Strike TTL number input

Item Types

Item Types represent the different types of entities on your platform. See Concepts → Item Type for details.

Configuration of an Item Type: a post from the firehose with a schema of fields that get sent to Coop including text, unique ID as well as what format the fields are in

When creating an Item Type, define the schema to include which fields will be included and shown to reviewers. These fields are also available in any rule logic to connect with signals for routing or automation.

Actions

Actions represent anything that can be performed on Items by proactive rules or moderator decisions. See Concepts → Actions for details.

Table of configured custom actions like: send warning, label as spam, delete content, delete account, ban email

Actions are paired with API enpoints on your platform. See Handling Actions for technical details.

Creating an action in Coop: add the name, description, what item types the action can run on, and a callback URL

Policies

Policies are the set of rules and guidelines that a platform uses to govern the conduct of its users. See Concepts → Policy for details.

Policy Dashboard showing 4 policies: Fraud, Nudity, Scams, Spam. There’s a button to create new policies as well as options to add sub-policies for each existing policy and edit or delete them

Policies added in Coop’s UI are visible to reviewers directly in the Job view of the Review Console.

User management

Coop uses role-based access controls to ensure the right people can access the right data.

User management page showing different users with different emails, roles assigned, approval status, and date created

You can invite users from Settings → Users, either copying the invite link to share directly or configuring an email service to send it automatically.

User invitation flow

Roles

Coop ships with seven default roles that cover most team structures out of the box:

  • Admin: manages the entire organization. They have full control over all resources and settings within Coop.

  • Rules Manager: can create, edit, and deploy Live Rules, run retroaction and backtests, view rule insights, manage policies, use the Investigation tool, and bulk-action content. They cannot manage users, queues, or other organization-level settings.

  • Moderator Manager: can view and edit all queues within the Review Console, manage moderator permissions, use the Investigation tool, and bulk-action content. They can also view child safety data.

  • Child Safety Moderator: the same permissions as Moderators, but can also review Child Safety jobs and see previous Child Safety decisions.

  • Moderator: can access the Review Console, but can only review jobs from queues they’ve been given permission to see. They cannot see any Child Safety-related jobs or decisions.

  • Analyst: can modify and test Draft and Background Rules, run backtests, and view rule insights and the Investigation tool. They cannot create or edit Live Rules, run Retroaction, or access the Review Console.

  • External Moderator: can only review jobs in the Review Console. They cannot see any decisions or use any other tooling.

Admins can customize any role under Settings → Users → Roles. Open the menu on any role card to edit its display name, description, and permissions; individual permissions are grouped by area (organization management, rules, manual review, and investigation) and can be toggled on or off. View Permissions opens a matrix comparing all roles at a glance.

Roles Management tab showing role cards for each of the seven default roles, with name, description, user count, and permission count

Changes apply immediately to every user assigned that role. Access to the role editor requires the Manage Roles permission, which Admins have by default.

API Keys

Coop uses API keys to authenticate requests between your platform and Coop.

Coop API key

To authenticate requests your platform sends to Coop, include your organization’s API key as an HTTP header on every request. You can find or rotate your key in Settings → API Keys.

X-API-KEY: <<apiKey>>
Content-Type: application/json

To verify that incoming requests to your Action endpoints were sent by Coop, use the webhook signature verification key shown in Settings → API Keys. See API Keys and Authentication in the Development Guide for implementation details.