Scan Profiles
Save and reuse scan configurations for different scenarios. Profiles let your team trigger scans with consistent settings without reconfiguring each time.
Creating a Profile
- Open the scan trigger modal on any repository.
- Configure your scan type and select a branch.
- Click Save as Profile and give it a descriptive name.
- The profile is saved to your organization and available to all members.
Using a Profile
When triggering a scan, saved profiles appear at the top of the scan trigger modal. Click a profile to auto-fill the scan type and branch. You can still override individual settings before triggering.
Examples
| Profile Name | Scan Type | Branch | Use Case |
|---|---|---|---|
| Production Audit | Deep | main | Full security audit before a release |
| Quick PR Check | Smart | develop | Fast feedback on the integration branch |
| Release Candidate | Deep | release/* | Comprehensive scan before cutting a release |
| Staging Verify | Smart | staging | Quick validation of staging deployments |
Managing Profiles
Profiles can be deleted by hovering over them in the scan trigger modal and clicking the delete icon. Only ORG_ADMIN and ORG_OWNER roles can create or delete profiles. All organization members can use existing profiles.
Scope
Profiles are scoped to your organization, not individual repositories. A profile can be used across any repository in your org. The branch specified in the profile must exist in the target repository for it to apply.