VyvernHelp Center

Recommended Autopilot Settings

Learn recommended Autopilot settings for onboarding, workflow approval thresholds, compliance review, and gradual automation rollout in Vyvern.

Last updated July 1, 2026

How should Autopilot be configured?

Vyvern recommends gradually enabling automation as your organization becomes more familiar with workflow behavior, proposal quality, and approval processes.

While Autopilot can significantly reduce administrative workload, starting with more conservative settings typically provides safer and more accurate onboarding.


Recommended Settings for New Organizations

For newly onboarded organizations, we generally recommend:

  • Lower auto-approval priority thresholds

  • Compliance review enabled

  • Limited eligible workflow categories

  • Manual review for higher-risk proposals

This allows organizations to validate:

  • Workflow quality

  • Organizational targeting

  • AI understanding of the environment

  • Persona realism and workflow behavior

before enabling broader automation.


Suggested Approval Thresholds

A common onboarding configuration includes:

  • Auto-approving Low and Medium priority workflows

  • Requiring manual approval for High and Critical priority workflows

This helps organizations:

  • Reduce unnecessary risk early on

  • Maintain oversight of advanced workflows

  • Evaluate workflow behavior before expanding automation

Many organizations increase approval thresholds gradually over time.


Compliance Review Recommendations

Vyvern strongly recommends keeping Require compliance review enabled during initial deployment.

Compliance review helps prevent workflows from being approved when:

  • Additional organizational validation is required

  • Restricted workflow categories are involved

  • Organizational policies require oversight

  • Workflow behavior needs additional verification

This is especially important for MSP deployments managing multiple organizations.


Gradual Automation Rollout

Most organizations benefit from enabling Autopilot in stages rather than immediately automating all workflow approvals.

A common rollout approach includes:

  1. Manual review of early workflows

  2. Limited Autopilot approval thresholds

  3. Expanding eligible workflow categories over time

  4. Increasing approval levels after workflow quality has been validated

This approach helps improve:

  • Workflow safety

  • Organizational trust in automation

  • Proposal quality validation

  • Long-term automation reliability


New Organization Review Period

For newly created organizations, Vyvern manually reviews the initial workflows generated by the AI before execution.

This additional review process helps ensure:

  • The AI understands the organization correctly

  • Workflow targets are valid

  • Platform restrictions are functioning properly

  • Generated workflows remain safe and realistic

During this period, some workflows may remain in a queued state pending review.


Recommended Workflow Categories for Automation

Organizations often begin by allowing Autopilot for:

  • Lower-risk awareness workflows

  • Information gathering workflows

  • Standard employee research proposals

Higher-risk workflow categories are often reviewed manually during onboarding and early deployment phases.


Long-Term Recommendations

After onboarding is complete, organizations may gradually:

  • Expand eligible workflow categories

  • Increase auto-approval priority thresholds

  • Reduce manual review requirements

  • Allow broader workflow automation

Vyvern recommends adjusting automation settings based on:

  • Organizational comfort level

  • Workflow quality

  • Employee awareness maturity

  • Compliance requirements

Recommended Autopilot Settings · Vyvern Help Center