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

# Media-buy approval

> What each media-buy approval choice does: manual means a person sees every buy, AI-assisted lets buys clearly within your policy go through, and automatic lets every buy through.

Your media-buy approval setting decides whether a person at your company sees a
buyer's new media buy before it goes live. There are three choices, and each
does exactly what it says.

| Choice | What happens to a new media buy |
| - | - |
| **Manual** | A person sees every buy. Every buy waits in your Approvals for your decision. |
| **AI-assisted** | A buy clearly within your written policy goes through. Every other buy waits in your Approvals for your decision. |
| **Automatic** | Every buy goes through without review. |

Choose one under **New media buys** in the approval gates on the AI Business
Rules page, ask Apostra, or save it on V3 with `save_business_rules`:

```json theme={null}
{ "mediaBuyApproval": "manual" }
```

The values are `manual`, `ai_assisted` and `auto`. Read the current one with
`get` and `kind: "business_rules"`. The setting applies to the media buys that
Apostra reviews for your storefront, and to buys created after you change it. A
connected sales agent or ad server may still apply its own review, and a media
company's own launches of its own supply are not queued. Creative and
new-buyer-account approval are separate settings and keep their own two
choices.

## Manual: a person sees every buy

With manual approval, nothing is booked until you decide. That includes a buy
that fits your Brief Acceptance policy perfectly.

Brief Acceptance still reads each buy against the policy you wrote, in any
language, when the buy arrives. Under manual it decides nothing. Its verdict is
shown beside the held buy in Approvals, so you can approve the clear ones
quickly and look closely at the rest:

* **Clearly within the policy.** The evidence supports approving.
* **Needs a look.** The evidence is thin, the policy is ambiguous, or a rule
  says this category needs review.
* **Clearly against a rule you wrote.** A strong signal to reject. Nothing is
  rejected for you, and the buyer is not told which rule matched.

Under manual and AI-assisted approval, a buy that fails a platform safety check
when it is created waits for your decision, whatever your policy says.

Open the Page with `open_approvals`, or ask Apostra to open your approvals. The
verdict appears when you open a held buy.

## AI-assisted: buys clearly within your policy go through

AI-assisted approval reads each buy against your Brief Acceptance policy when it
arrives. A buy goes through without review only when the policy clearly covers
it and an independent second check agrees. A buy that needs a look, clearly
breaks a rule, or could not be checked waits in Approvals, and so does a buy
held by the [over-forecast policy](https://docs.apostra.com/v3/seller-guaranteed-availability.md). Nothing
is rejected for you.

Moving from manual to AI-assisted means some buys go live without a person
seeing them, so Apostra asks you to confirm before it saves. Send
`acknowledgeNoHumanReview: true` with the change:

```json theme={null}
{ "mediaBuyApproval": "ai_assisted", "acknowledgeNoHumanReview": true }
```

Moving from AI-assisted back to manual adds review and needs no confirmation.

## Automatic: every buy goes through

Automatic approval creates every buy without review. Brief Acceptance still
qualifies product discovery, and a buy that passes discovery is created with no
second check at create time, including no platform safety check. Moving to automatic needs the same confirmation,
`acknowledgeNoHumanReview: true`.

## If you set manual before this changed

Before, manual approval let a buy through when Brief Acceptance read it as
clearly within your policy, and held only the others. That is now the
AI-assisted choice. Manual now means a person sees every buy, and storefronts
already on manual keep manual. If you want the earlier behavior, choose
AI-assisted as above.


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