> ## Documentation Index
> Fetch the complete documentation index at: https://docs.moderationapi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Actions

> Actions are the verbs of moderation — what moderators (and automation) do to content and users.

An **action** is anything that can run against a piece of content or a user: rejecting a comment, blocking an author, sending a warning, removing a profile from your app. Each action is configurable, can carry a value (a reason, a category, a duration), and can fire a [webhook](/actions/webhooks) so your application reacts in real time.

Actions live in two flavors:

<CardGroup cols={2}>
  <Card title="Content actions" icon="file-lines" href="/actions/content-actions">
    Run on individual queue items. Built-in **reject** and **allow**, plus any custom actions you create — "Hide post", "Send to legal", "Flag for review", etc.
  </Card>

  <Card title="Author actions" icon="user" href="/actions/author-actions">
    Run on the user behind the content. Built-in **block**, **suspend**, and **enable**, plus custom author-level actions like warnings or feature restrictions.
  </Card>
</CardGroup>

## How actions are used

* **In the dashboard.** Moderators run actions from the queue or user detail pages. Custom actions appear alongside the built-ins.
* **Programmatically.** Call the [execute action endpoint](/api-reference/actions/execute-moderation-action) to run any action — built-in or custom — against content or authors from your own systems.
* **As webhook triggers.** Every action that runs fires a [webhook event](/actions/webhooks) (`queue_item.rejected`, `author.blocked`, `queue_item.action`, etc.) so you can sync state back to your application.

## Built-in vs. custom

Built-in actions cover the common cases — rejecting content, blocking authors, and so on. If they don't cover what you need, you can create custom actions to fit your workflow.

|                   | Built-in                                                | Custom                                          |
| ----------------- | ------------------------------------------------------- | ----------------------------------------------- |
| **Created by**    | The system                                              | You                                             |
| **Examples**      | Reject, allow, block, suspend, unblock                  | "Hide post", "Send warning email", "Escalate"   |
| **Webhook event** | Dedicated event per action (e.g. `queue_item.rejected`) | Generic `queue_item.action` or `author.action`  |
| **Configurable**  | Possible values, queue visibility                       | Everything: name, level, values, queue behavior |

Configure actions under [**Configure → Actions**](https://dash.moderationapi.com/project/latest/configure/actions) in the dashboard.

## What's next

<CardGroup cols={3}>
  <Card title="Content actions" icon="file-lines" href="/actions/content-actions">
    Reject, allow, and custom item-level actions.
  </Card>

  <Card title="Author actions" icon="user" href="/actions/author-actions">
    Block, suspend, enable, and custom user-level actions.
  </Card>

  <Card title="Webhooks" icon="bolt" href="/actions/webhooks">
    Receive real-time events when actions run.
  </Card>
</CardGroup>