Skip to main content
The Settings page gives organization admins a central place to manage security and automation preferences. You can access it from Settings in the dashboard sidebar.

​
Severity Thresholds

Severity thresholds filter out vulnerability findings below a configured level so your team can focus on what matters most. There are two independent thresholds:
  • Code Generation: applies to vulnerability findings surfaced during AI-assisted coding sessions.
  • CI / Pull Requests: applies to vulnerability findings surfaced during CI checks and pull request reviews.
Each threshold can be set to one of the following severity levels:
  • Critical
  • High (default)
  • Medium
  • Low
  • Info
Vulnerability findings below the selected level are suppressed from results. For example, setting the threshold to High means Medium, Low, and Info vulnerability findings will not be shown. Thresholds are configured per organization and apply to all repositories within it.

​
Auto-Remediation

Auto-remediation controls whether Asymptote automatically creates draft pull requests with security fixes for SCA findings and codebase scans. Draft PRs are only created when a fix is available.

​
Organization-Level Threshold

Admins can set a minimum severity level at which Asymptote automatically creates draft PRs:
  • Critical: only auto-remediate critical vulnerabilities
  • High: auto-remediate high and critical vulnerabilities
  • Medium: auto-remediate medium, high, and critical vulnerabilities
  • Low: auto-remediate all vulnerabilities
  • Off: disable auto-remediation entirely (fixes are stored but no PRs are created)

​
Per-Repository Overrides

Below the org-level setting, admins can override the auto-remediation threshold for individual repositories. Each repository can be set to:
  • Default: inherits the organization-level threshold
  • Off: disables auto-remediation for that specific repo
  • Critical / High / Medium / Low: overrides with a repo-specific threshold
This is useful when certain repositories need stricter or more relaxed auto-remediation policies than the rest of the organization.

​
Deferred Remediation PR Creation

When auto-remediation is off, either at the org level or via a per-repo override, admins can still manually create remediation PRs from the dashboard if a fix is available.

​
Scan Schedules

Scan schedules let you enable daily automated scans for individual repositories. When enabled, a scan runs every day at 3:00 AM UTC and includes the same scan types available when running a scan on demand. To configure scan schedules:
  1. Go to Settings in the dashboard
  2. Find the repository you want to configure
  3. Toggle the schedule on or off

​
Access

The Settings page is restricted to organization admins. Members without admin privileges will not see the Settings option in the dashboard.