Settings and AutoPilot

Settings is where ASAPilot moves from generic analysis to your operating model. The page is split into four tabs, each controlling a different layer of behavior.

New workspaces start with recommended defaults for Persona, Audit Configuration, and AutoPilot Configuration, so the page is usable on first load before any manual tuning.

Agent Persona (Soul)

Tune persona name, personality, communication style, risk tolerance, core values, and custom instructions so responses match your operating style.

Audit Configuration

Set thresholds and report-shaping rules for audit pace, learning windows, dead-keyword timing, CPA multiples, pacing thresholds, weekend multipliers, and report depth.

AutoPilot Configuration

Control execution policy, chat confirmations, automation run mode, enrolled apps, per-app overrides, and stage-level write permissions.

User Preferences

Set language, currency, timezone, reporting detail, notification email, and personal defaults that shape the rest of the product.

What AutoPilot controls today

• Execution Policy: chat scope confirmation, stage confirmation, default date window, and optional anomaly/search-match stages.
• Automation Run Mode: dry run, apply safe stages, or apply all allowed stages.
• Automation Enrollment: choose which apps are eligible when the run mode uses enrolled-only scope.
• Default Operating Baseline: classify apps by category and lifecycle, then set optimization goals and budget mix.
• Per-App Overrides: replace the default policy for a specific app or org scope when one portfolio segment needs different rules.
• Advanced Stage Controls: enable or disable Waste Control, Bid Optimization, Search Term Promotion, Keyword Expansion, and Budget Allocation with change and spend guardrails.

Recommended rollout order

Start with Preferences so timezone, currency, and reporting defaults are correct.
Set Persona and Audit Configuration before judging response quality, otherwise the output style may still be generic.
Keep AutoPilot conservative first: verify enrolled apps, review stage policies, and only widen automation authority when the reporting loop is already trusted.
Use per-app overrides only when one app genuinely needs different lifecycle, budget, or optimization goals.

Important operational note

AutoPilot exposes guarded execution controls, but policy should still be treated as intentional infrastructure. Do not widen write permissions just because a workflow exists. Configure scope, guardrails, and review habits first.

Apply settings to automations

Use the Automations guide to turn policy into recurring workflows.

Check plan limits

If a setting rollout is blocked by capacity, confirm your current plan and limits.