Approvals

Your employee can draft, research and plan on its own. It cannot ship or spend on its own. Those steps become approval requests that a person decides.

What needs an approval

• Publishing anything (an article to WordPress, a post, an email)
• Launching or changing a paid campaign
• Any action with a cost above what is already budgeted for the job

How a request looks

Each request has an action (for example publish), a title, a summary of what will happen, an optional estimated cost, and the brand it belongs to. It starts as pending.

Who decides

Owners and admins approve or reject. Editors and the employee can create requests but cannot decide them. A decided request cannot be changed; if something needs to change, the employee files a new request.

Every decision is written to the audit log with who decided, when, and the note they left.

Where to find them

The Overview page shows how many requests are waiting. The approval inbox with full details arrives together with Growth Missions. Developers can already use the /approvals endpoints, see the API overview.