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

# Approvals

> What waits for a person's yes, how your agent asks for it, and where you give it.

Your agent can ask for an approval. It can never give one. You give it on a page inside the OpenEmail app in your Shopify admin, after Shopify confirms who you are.

## What needs an approval

Anything that means more email, or brings people in as subscribers, waits for a staff member:

| What | How it's asked for | What the approval is bound to |
| - | - | - |
| A campaign going out | Your agent: `request_approval`, kind `campaign` | The email version, the list and its revision, the set time or "now", and the most recipients it may reach |
| Resuming a campaign OpenEmail paused | Your agent: `request_approval`, kind `campaign` | That one pause |
| A flow version going live | Your agent: `request_approval`, kind `flow` | The flow's steps and waits, with each step's email version as it was saved |
| A Klaviyo migration | Your agent: `request_approval`, kind `klaviyo_migration` | The read of your Klaviyo account, and how many contacts it makes subscribed |
| A hand subscribe | Your agent: `prepare_hand_subscribe`, or you on **Contacts > Hand subscribe** | The statement of how people agreed, and their exact addresses |
| A test address other than your own | Your agent: `add_test_address`, or you on **Settings > Test addresses** | That address |
| Lifting a hand-added do-not-email entry | Your agent: `lift_do_not_email_entry`, or you with **Lift entry** on **Contacts > Do-not-email list** | That entry |
| Confirming there's no Klaviyo account | Only you, with **Confirm no Klaviyo account** on **Settings > Klaviyo** | Lifting the Klaviyo hold |

Where a screen in the admin shows exactly what an action does, doing it there is the approval. It's checked with Shopify and recorded with your staff account, the same as on an approval page.

What never needs one: anything that means less email or only reads. Unsubscribing a contact, adding an address to the do-not-email list, pausing or cancelling a campaign, turning a flow off, cancelling a migration, withdrawing a request and exporting contacts all go through at once. Allowing an agent to connect is its own step on the **Connect** screen, and your yes to an update is said to your agent, not given here.

## Approve a request

**1. Your agent asks**

* Your agent saves the thing first (a campaign, a flow draft, a migration read), then asks for your approval and gives you a link like `https://email.yourstore.com/approvals/<id>`.
* Asking freezes the thing as it is at that moment. The request is bound to those figures and to an upper limit on each one that means more email, so nothing past them can happen under it.
* Your agent can check on the request with `get_approval`, which waits up to four seconds for your decision.

> [!TIP]
>
> **Checkpoint:** your agent has given you a link, not a code or a question to answer in chat.

**2. Open it in your Shopify admin**

* Open the link in a browser signed in to Shopify. It lands on the request's page in the OpenEmail app.
* Or open **Approvals** in the app's menu. **Open** lists requests waiting for a decision; **Past** lists the ones approved, declined, withdrawn, voided, ended or expired.
* The page starts with **What you're approving**: the figures the approval is bound to, the most it allows (for example "Allows at most 2 addresses") and what approving does. If something needs your attention, one banner below it says so.
* **Who asked** names the agent, whether its details came from its own domain (**Verified**) or from the agent itself (**Not verified**), and which staff member allowed its connection. **Times** shows when it was asked and when it expires.
* The figures and wording on the page come from OpenEmail itself, never from your agent's summary.

> [!TIP]
>
> **Checkpoint:** the figures on the page are the ones you expected.

**3. Approve, decline or withdraw**

* The decision buttons are at the top of the page. Each opens a question first, and nothing happens until you confirm it.
* **Approve** restates the figure, for example "Approve subscribing 2 addresses?". OpenEmail runs its checks again at that moment, then makes the change itself, at once or at the time it names. If a check fails, nothing changes, the request stays open and the page shows the reason.
* **Decline** ends the request without the change. It can't be undone; the change needs a new request.
* **Withdraw** ends a request without a decision, or an approval that hasn't taken effect yet. Withdrawing a scheduled campaign's approval puts the campaign back in draft.

> [!TIP]
>
> **Checkpoint:** the request moves to **Past** with its new state, and your decision shows on **Settings > Activity** under your name.

Your agent can withdraw too, with `withdraw_approval`. Withdrawing can't be undone either.

## When a request ends on its own

* **It expires** 24 hours after your agent asks. An expired request can't be approved; ask your agent to ask again.
* **The thing changes.** A new email version, another list, contacts added to the list, a new set time: any edit that could mean more email ends the request, and ends an approval that hasn't taken effect. The page says "What it was about was changed, so it needs a new request." Renaming a campaign or lowering its recipient limit keeps the approval.
* **A newer request replaces it**, or the agent's connection ends.
* **A check fails at the click.** For example, a Klaviyo read more than 7 days old can't be approved; ask your agent for a new one.

If the page can't tell whether your decision went through (the connection dropped, say), it says so and offers **Open Activity**. Check there before trying again, because the decision may already be recorded.

## Why a chat message never counts

Your agent writes everything you read in chat. A summary there can be wrong: it can say two people when the list it built holds hundreds. So OpenEmail never takes a "yes" in chat, an approval code relayed by your agent, or a click on an emailed link. The only approval is a click on a page OpenEmail controls, behind Shopify's own sign-in, showing OpenEmail's own figures to a person your agent can't stand in for.

That also means your agent never makes a "commit" call after you say yes. **Approve** applies the change by itself.

Any staff member Shopify lets open the app can decide, collaborators included, and the record marks a collaborator as one. The store owner controls who that is in Shopify's app permissions for staff and collaborators.

> [!WARNING]
>
> **Keep the click yours.** An agent driving a browser that's signed in to Shopify could press **Approve**, and OpenEmail would see only the signed-in staff member. An agent holding your Render or Shopify CLI credentials has an operator's access, beyond any approval. Decide which agents get either.

> [card] [Campaigns](https://openemail-docs.mintlify.site/use/campaigns.md)
>
> What a campaign approval checks before it schedules the send.

> [card] [Flows](https://openemail-docs.mintlify.site/use/flows.md)
>
> How a flow version goes live, and how to turn it off.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.