# AI Actions

### Overview

The **AI Actions** tab in the Pages module allows administrators to automate page approval workflows, ensuring that content is reviewed and validated before it is published. This capability introduces structured governance into the page lifecycle by combining AI-driven review with configurable human approvals.

<figure><img src="/files/zqbuRM4FQyA4QoaTuQf9" alt="" width="563"><figcaption></figcaption></figure>

Accessible via **Admin Portal → Domain → Pages → AI Actions**, this section provides centralized control over approval workflows applied to pages across the domain.

AI Actions enable administrators to define automated workflows that are triggered when a page is published or republished. These workflows guide pages through a series of approval steps before they become visible, helping maintain content quality and compliance with organizational standards.

A default workflow is available out of the box and can be activated, modified, or extended as needed. Administrators can manage all workflows from a single interface, including viewing usage, status, and recent activity.

***

### Workflow Configuration

Each AI Action consists of three core components: a trigger, optional conditions, and a sequence of actions.

<figure><img src="/files/qY9Tz7NWWuf2Xei2bsjm" alt="" width="563"><figcaption></figcaption></figure>

The **trigger** defines when the workflow begins, such as when a page is published or republished. Once triggered, optional **conditions** can be applied to determine whether the workflow should run. These conditions can be based on attributes like page author or team, allowing workflows to target specific content scenarios.

The **action sequence** defines what happens after the workflow is triggered. This typically includes sending the page for AI review, routing it to specific users or teams for approval, and publishing the page once all approvals are completed. Administrators can configure up to two levels of approval, using a combination of AI and human reviewers.

***

### Approval Flow

When an active workflow applies to a page, the publishing process changes from immediate publication to a structured approval flow. Instead of going live instantly, the page enters a **Pending Approval** state.

<figure><img src="/files/4mWYl6uDy7uw2Lw3taIe" alt=""><figcaption></figcaption></figure>

Approvers receive requests through notifications and can review, approve, or decline the page. If approved at all required levels, the page is published automatically. If declined at any stage, the workflow stops and the author is notified.

{% hint style="success" %}
Only **one approval workflow can be active per page at a time**, ensuring a clear and consistent approval process.
{% endhint %}

***

### Management and Visibility

The AI Actions tab provides visibility into all configured workflows, including their status (active or inactive), usage count, and last used date. Administrators can edit workflows, deactivate them, or view logs to track activity and changes over time.

Detailed logs are available to track execution, configuration changes, and usage, providing full transparency into how workflows are applied and how often they are triggered.

***

### Key Considerations

AI Actions introduce governance without requiring manual intervention for every page. Workflows can be tailored to apply broadly or only under specific conditions, giving administrators flexibility while maintaining control.

Once a workflow is active, it automatically applies whenever its trigger and conditions are met. Pages already in an approval state are not affected by changes made to the workflow after submission.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guides.mangoapps.com/admin-guide/domain-settings/pages/ai-actions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
