Write policies per client: observe, propose or auto
Different clients need different levels of automation. The write policy sets it per client — from read-only to automatic application of safe changes.
What it does
Observe: the service reads and analyzes, but no proposals can be created for the client. Propose (default): every change waits for a human approval. Auto: reversible changes within limits — budgets, statuses at every level, negative keywords and the final URL suffix — are applied without a manual approval; everything else still waits.
The policy also holds the client's limits and the “writes paused” switch. Turning on auto requires the second factor, and changes like targeting, bidding strategy or keywords always need a person.
Why it helps
- Match automation to the client's trust and risk.
- Safe automation: only reversible changes within limits are automatic.
- Pause all writes for one client without affecting others.
How to set it up
- Open Clients (or the client's settings) → “Write policy”.
- Choose observe, propose or auto.
- Set limits and the daily budget cap.
- Confirm with the second factor when enabling auto.
Good to know
- Automatic reactions to anomalies use the same policy.
- The workspace emergency stop overrides every client policy.



Try it on your own accounts
Create a workspace, connect Google or Meta in a couple of clicks and see your accounts clearly. Changes follow your approvals or the policy you configure.
Create your workspace