Enabling Autopilot

You can enable Autopilot at three scopes. The most specific scope always wins — a domain override beats an organisation setting, which beats the account default.

Option A: Account-Wide Default

Sets Autopilot as the default for all domains with no override.

Go to Settings → Automation
Select Autopilot (Level 3) from the four-card selector
Save. All domains without an org or domain override now run on Autopilot.

Option B: Per-Organisation

Sets Autopilot for all domains in a specific organisation, overriding the account default.

Go to Alerts → Organisations
Find the organisation and click the automation level badge next to its name
Select Autopilot in the change modal and confirm

Option C: Per-Domain Override

Sets Autopilot for a single domain, overriding both account and organisation settings.

Go to the domain's dashboard
Navigate to the Autopilot section
Use the domain-level automation level control to set it to Autopilot

Prerequisites Before Enabling

☑ DMARC reports are being received (domain has a valid rua address configured)

☑ Existing email sources have been reviewed so Autopilot inherits a clean baseline

☑ No unresolved Critical authentication failures on the Security Dashboard

☑ SPF delegation is active (managed SPF configured) so Autopilot can write to your SPF record

What Changes When Autopilot Activates

Setting	Before	After Autopilot
SPF source approval	Manual decision required	Automated (high-confidence sources auto-approved)
DMARC progression	Waits for manual trigger	Runs automatically on schedule
DKIM monitoring	Alerts only	Alerts + auto-pauses progression on critical issues
SPF page indicator	No indicator	Purple "Managed by Autopilot" badge appears

Visual Indicators

When Autopilot is active for a domain, you'll see purple "Managed by Autopilot" badges on the SPF Management page and DMARC Progression settings. The manual approval controls are locked to prevent conflicting with automated decisions.

Enabling Autopilot