Why are organizational restrictions important?
Vyvern is designed to operate within the comfort level, security requirements, and compliance expectations of each organization.
Every organization has different:
Risk tolerances
Internal policies
Compliance requirements
Platform restrictions
Security expectations
Because of this, Vyvern allows organizations and MSPs to configure restrictions around how workflows are generated, reviewed, and executed.
Workflow Restrictions
Organizations can restrict:
Specific workflow categories
High-risk workflow types
Certain targeting behaviors
Automatic approval thresholds
Advanced workflow operations
This allows organizations to maintain greater control over how testing is performed within their environment.
Compliance Restrictions
Organizations may also require:
Manual workflow approval
Compliance review before execution
Additional oversight for specific workflow types
Restricted Autopilot behavior
These safeguards help ensure workflows align with organizational policies and operational requirements before execution.
Platform & Environment Restrictions
Some workflows may also be restricted based on:
Demo vs production environments
Resource-intensive workflow operations
Platform-specific limitations
Organizational deployment stage
For example:
Demo environments intentionally restrict certain advanced functionality
Newly onboarded organizations may have additional workflow review requirements
Certain operations may require elevated approval thresholds
Workflow Filtering & Approval Controls
Vyvern allows administrators to configure:
Which workflows are eligible for Autopilot approval
Maximum auto-approval priority levels
Workflow category restrictions
Compliance review requirements
This helps organizations gradually increase automation while maintaining oversight and safety.
Organizational Comfort & Safety
One of Vyvern’s primary goals is ensuring organizations remain comfortable with the testing being performed within their environment.
Organizations should feel confident that:
Workflow behavior aligns with expectations
Approval systems are functioning correctly
Unsafe or unrealistic workflows are filtered appropriately
Administrators maintain meaningful oversight and control
This is especially important during onboarding and early deployment phases.
Adaptive Restrictions Over Time
As organizations become more familiar with Vyvern, many choose to:
Expand eligible workflow categories
Increase Autopilot approval thresholds
Reduce manual review requirements
Enable more advanced workflow behavior
Restrictions can be adjusted over time based on:
Organizational maturity
Security awareness levels
Workflow confidence
Internal compliance requirements