Actions and Approvals
How do approved changes get decided safely?
Example finding
Govern one action class at a time
Set structured data fixes to auto approve and new page content to need approval, and both decisions are guardrail checked and logged the same way.
Quick answer: Actions and Approvals
Actions and Approvals is the governance layer: Agent policies, an approval center and a guardrail check on every decision, so nothing proceeds on a gated action class without a logged approval. Carrying out the change is still yours; a connected CMS that executes it for you is not built yet.
What you see
Set each action class to recommend only, need approval, or auto approve in Agent policies. Every action routed through approval or auto approval runs a guardrail check first, and the decision is recorded. Carrying out the underlying change is still yours; a connected CMS that applies it for you is not built yet.
Approval center
Approve or reject each action from a class you set to need approval, with the evidence attached.
Agent policies
Set each action class, in Settings, to recommend only, need approval, or auto approve.
Guardrail check
Every approval and auto-approval is checked; an action that targets a domain other than this brand's own is always blocked, whatever the policy says.
Decision record
Who decided, when, and the outcome, feeding the Activity timeline.
How it works
- 1
Set a policy
Choose, per action class, whether it stays recommend only, needs approval, or can auto approve.
- 2
Decide
A gated action is approved or rejected, with a guardrail check run either way.
- 3
Carry it out
You or your team make the change today. A connected CMS that executes an approved action automatically is next.
How it is measured
Definitions come first, so numbers stay comparable from one audit to the next.
- Approval record
- Who decided, when, and the action's payload and scope.
- Policy level
- Recommend only, needs approval or auto approve, set per action class.
- Guardrail events
- Blocked actions, logged with the reason.
Good to know. Live today as a decision and guardrail layer. What it does not yet do is make the change for you: no CMS is connected, so an approved action still needs you or your team to carry it out, and there is nothing yet to roll back.
Common questions
Will anything change my site without approval?
Nothing is applied to your site automatically at all today, approved or not. What approval and policy govern is the decision to proceed; carrying it out is still a manual step.
Which CMS is supported first?
None yet. Governance (policies, approval, guardrails) is live; a connected CMS that executes an approved change for you is the next step, chosen from early customer demand.
Will it execute without approval?
Nothing executes on your site, with or without approval. Approval and policy govern the decision to proceed; you still make the change.
A short checklist
- Set the policy level per action class in Settings
- Review each pending action's evidence
- Approve or reject
- Confirm the guardrail passed
- Carry out the change yourself, then verify
Who uses it
- Marketing lead
- Approve with confidence, and a clear log of who decided what.
- Compliance
- Policy and an append only decision trail.
- Web team
- A clear scope and payload to apply by hand.
Common mistakes
Setting every class to auto approve at once
Start with approval on classes that matter, then widen auto approve as you trust the pattern.
Skipping scope checks
Guardrails exist for a reason, and block a mistargeted domain regardless of policy.
Expecting it to execute the change
Approval governs the decision, not the execution. No CMS is connected, so you still make the change.
See Actions and Approvals on your own brand.
Start with a first audit. We show where you appear, who is named instead, and what to fix first.