Wavo Limits & Autonomy — guardrails for the AI copilot
Set per-team WAVO guardrails in Wevion at Settings → Team → Wavo Limits: kill-switch, spend caps, approval, protected entities and undo. Owner-only.
Written By Salvatore Sinigaglia
Last updated About 2 hours ago
Set per-team WAVO guardrails in Wevion at Settings → Team → Wavo Limits: kill-switch, spend caps, approval, protected entities and undo. Owner-only.
Wavo Limits & Autonomy — guardrails for the AI copilot
Wavo Limits & Autonomy is the control panel that governs what the Wevion AI copilot (Wavo) is allowed to do on your ad accounts. It lives at Settings → Team → Wavo Limits (
/settings/team/wavo-limits) and is available to super_admin, admin, and owner roles. Every setting is per team and can only make Wavo stricter than the global configuration — a global kill-switch that is off always wins over any team value. Changes save instantly and are recorded in the audit log.
Who is this for
Team owners and admins who let Wavo take autonomous or assisted actions (pausing entities, changing budgets, launching campaigns) and want to bound that power — spend ceilings, approval gates, protected campaigns, and a one-click stop.
How the settings resolve
Wavo reads a resolved configuration for each team: it starts from the global (platform-wide) defaults and layers your team's overrides on top. A banner at the top of the page tells you how many keys this team currently overrides ("some overridden" vs "all default").
- Applica consigliato / Apply recommended profile — fills the recommended safe values in one click.
- Reset to global — clears this team's overrides so it re-inherits the global config (only shown when at least one override exists).
Because guardrails are per team, the page needs a team context. If your active scope is not a team (for example a founder on the organization scope), an inline team picker appears so you can manage a specific team's limits without switching your global scope. Wevion never auto-selects a team for multi-team users, so the pick stays explicit.
Backend: GET /api/v1/teams/:teamId/guardrails returns the resolved values, global defaults, team overrides, recommended values and the source of each key. PATCH (owner/admin/super_admin) upserts overrides; DELETE resets them.
The kill-switch (top of the page)
The kill-switch is always pinned at the top and turns visibly red when Wavo autonomy is off.
- Autonomy kill-switch — the master toggle. When off, Wavo stops taking autonomous actions.
- Kill-switch scope — choose what the switch covers:
autonomous_only— stops only fully autonomous actions.plus_rest_bulk— also stops REST/bulk-driven actions.
- Pause autonomy — a temporary pause with presets of 1, 4, or 24 hours (
autonomy_paused_until). While active, a badge shows the live countdown and a Resume button lifts it early.
Spend ceiling
Approval gates
Route high-impact actions through a human before they execute.
- Approval enforcement — turn the approval workflow on or off.
- Approval min role — the minimum role that may approve a request (mediabuyer, manager, owner, admin, super_admin). Recommended: manager.
- High-impact min role — a stricter minimum role for high-impact actions.
- Always require approval for — pick the verbs that always need approval, chosen from launch, reactivate, and increase budget.
- Approval request TTL — how long a pending approval stays valid, in minutes (5–1440).
Scope: where Wavo may act
- Protected entities — a blacklist of campaigns, ad sets, or ads Wavo must never touch. Add each entry by entity type, entity ID, and optional platform (this is the strongest protection and is shown first, in red).
- Time windows — restrict autonomous actions to specific hours and days. Set start/end times (HH:MM), pick weekdays (or leave empty for every day), and optionally a timezone.
- Allowed platforms — a comma-separated allow-list (e.g.
meta, taboola). - Allowed ad accounts — a comma-separated allow-list of ad account IDs (e.g.
act_123).
Action types
Control each kind of action Wavo can perform. Some are simple on/off switches; others are three-state selects.
Three-state options are allow (true), block (false), or require approval (approval).
Safety & log
- Undo enabled — allow reversing Wavo actions.
- Undo window — how long an action stays reversible, in minutes (5–1440).
- Action log visible — controls whether non-owner members can see this team's Wavo action log.
- Notify on action — sends an in-app inbox notification to the team owner after a Wavo action.
- Notify minimum risk — only notify at or above this risk level: LOW, MEDIUM, or HIGH.
Undoing a Wavo action
When undo is enabled and the undo window has not expired, a reversible action can be rolled back. Wevion re-applies the inverse operation on the live ad platform through the same action handler, restoring the previous state.
- Reversible action types: toggle entity status and update entity budget.
- Only successfully executed actions can be undone, once each (a second undo of the same action is rejected).
- The undo runs under your access and tokens, so you can only undo entities you can reach.
Backend: POST /api/v1/ai-action-log/:id/rollback.
Roles and audit
- Reading the guardrails page requires super_admin, admin, or owner.
- Saving or resetting overrides requires owner, admin, or super_admin; a team owner can tighten but not loosen the global config.
- Every save and reset is written to the audit log with the changed keys and their old/new values.
FAQ
Where do I set Wavo's limits in Wevion?
Open Settings → Team → Wavo Limits (/settings/team/wavo-limits) as a super_admin, admin, or owner. The page groups controls into kill-switch, spend ceiling, approval gates, scope, action types, and safety & log. Every setting is per team, saves instantly, and is recorded in the audit log. Use "Apply recommended profile" to fill safe defaults or "Reset to global" to clear this team's overrides.
How do I stop Wavo immediately?
Use the kill-switch pinned at the top of the Wavo Limits page — turning it off halts Wavo's autonomous actions, and the card turns red to confirm. Set the kill-switch scope to plus_rest_bulk to also cover REST and bulk-driven actions. For a temporary stop, use the pause presets (1, 4, or 24 hours), which show a live countdown and can be resumed early.
Can a team owner make Wavo more permissive than the platform default?
No. In Wevion, per-team guardrails can only make Wavo stricter than the global configuration. The engine combines a global kill-switch that is off over any team value, so a team owner can tighten limits — lower caps, more approvals, more protected entities — but cannot re-enable something the platform has disabled globally.
Which Wavo actions can be undone?
Undo covers reversible actions — toggling an entity's status and updating an entity's budget — when undo is enabled and the configured undo window has not expired. Only actions that executed successfully can be rolled back, and each can be undone only once. The undo runs under your own access and tokens, restoring the previous state on the live platform via POST /api/v1/ai-action-log/:id/rollback.
Who gets notified when Wavo acts?
When Notify on action is on, Wevion sends an in-app inbox notification to the team owner after a Wavo action. You can throttle noise with Notify minimum risk (LOW, MEDIUM, or HIGH) so only actions at or above that risk level trigger a notification. All actions are also captured in the team's Wavo action log, whose visibility to non-owner members is controlled by the Action log visible setting.
FAQ
Where do I set Wavo's limits in Wevion?
Open Settings → Team → Wavo Limits (/settings/team/wavo-limits) as a super_admin, admin, or owner. The page groups controls into kill-switch, spend ceiling, approval gates, scope, action types, and safety & log. Every setting is per team, saves instantly, and is recorded in the audit log. Use "Apply recommended profile" to fill safe defaults or "Reset to global" to clear this team's overrides.
How do I stop Wavo immediately?
Use the kill-switch pinned at the top of the Wavo Limits page — turning it off halts Wavo's autonomous actions, and the card turns red to confirm. Set the kill-switch scope to plusrestbulk to also cover REST and bulk-driven actions. For a temporary stop, use the pause presets (1, 4, or 24 hours), which show a live countdown and can be resumed early.
Can a team owner make Wavo more permissive than the platform default?
No. In Wevion, per-team guardrails can only make Wavo stricter than the global configuration. The engine combines a global kill-switch that is off over any team value, so a team owner can tighten limits — lower caps, more approvals, more protected entities — but cannot re-enable something the platform has disabled globally.
Which Wavo actions can be undone?
Undo covers reversible actions — toggling an entity's status and updating an entity's budget — when undo is enabled and the configured undo window has not expired. Only actions that executed successfully can be rolled back, and each can be undone only once. The undo runs under your own access and tokens, restoring the previous state on the live platform via POST /api/v1/ai-action-log/:id/rollback.
Who gets notified when Wavo acts?
When Notify on action is on, Wevion sends an in-app inbox notification to the team owner after a Wavo action. You can throttle noise with Notify minimum risk (LOW, MEDIUM, or HIGH) so only actions at or above that risk level trigger a notification. All actions are also captured in the team's Wavo action log, whose visibility to non-owner members is controlled by the Action log visible setting.
Last updated: 2026-07-02