Open Banger ↗
Skip to content

Approvals, logs & sending

Approvals

What needs a person's approval, how to set the threshold, and how to approve, reject, or revise a request.

2 min readUpdated
In this guide 4 sections

Approvals is where a person signs off on what your AI or the API wants to do. Open Approvals. Home shows how many are waiting.

What needs approval

Set it under When do sends need your approval? › Edit:

  • Every send
  • Large sends (recommended): more than a number of people you choose. Default 50.
  • Never

These always need a person, whatever the setting:

  • turning on a new Journey, or one that changed
  • publishing a shared layout
  • domain changes and email migrations

When you do something yourself in the app, like sending a Broadcast or turning on a Journey, that counts as the approval. Requests from your AI or the API wait here.

Decide

Open a request to see exactly what will happen. Then:

  • Approve or Reject, with an optional note for the record.
  • Revise request to change it. This creates a new request, and the original stays in history.

Only a signed-in person can decide. API keys can’t approve anything. If the request changed after you opened it, the decision fails, so you never approve something you didn’t see.

Several requests of the same kind can be handled together with Approve all or Cancel all.

Missed requests

Requests expire after 24 hours and move to Missed. Choose Re-request or Dismiss.

Try it with your AI

List everything waiting in Approvals, explain each one in a sentence, and tell me which are risky.

Still stuck? Contact support with the screen and the exact error.