Archive scans, findings, and history

Outcome

You can hide finished or irrelevant history from a repository's default view — a single deduped finding, a whole scan, or an entire environment with everything under it — and bring any of it back with one filter. Archiving is fully reversible and never deletes data: it flips a display flag, and unarchiving restores the item exactly as it was.

Who can do it

• Capability: archiving requires the archive permission. Customers hold it by default; an invited organization member holds it through their seat's default grants (and only on repositories in their granted access, or via the Repo owner role on one repository); site admins hold it everywhere. Waitlist accounts and members holding only the Findings reviewer role cannot archive.
• Ownership, per item: an environment can be archived by a user who owns a build that produced it (or a site admin); a scan by the user who launched it (or a site admin); a finding group by any user who owns a scan of this repository (or a site admin).

Before you begin

• The repository needs existing history — environments, scans, or findings (see Run a security scan).
• Understand the blast radius: archiving an environment hides it and all scans and findings under it from the default view. Archiving a single finding group or scan hides only that item.
• Archiving is not deletion. Deleting a job is a separate, irreversible action on the job's detail page — prefer archiving, which you can always undo.
• Archiving only changes what is displayed. A future scan can still report the same underlying issue; to teach scans, record a review decision or pin accepted behavior instead (see the Troubleshooting section below).

Steps

1. Open Attack surface in the top navigation and select the repository.
2. Archive one finding: on the Findings tab, find the row and select its small archive button (tooltip: “Hide this deduped finding from the default view (e.g., false positive)”).
3. Archive one scan: on the Environments & hunts tab, find the scan entry under its environment and select archive.
4. Archive a whole environment: on the same tab, select Archive env on the environment header and confirm the prompt (“Archive env <name>? All hunts and findings under it will be hidden by default.”).
5. See what is archived: in the filter row, select Include archived (N). Archived items reappear dimmed with an archived badge, and the button changes to Hide archived.
6. Restore: with archived items visible, select unarchive on a finding or scan, or Unarchive env on an environment.

Verification

• The archived item disappears from the default view immediately.
• With Include archived (N) active, the item is shown dimmed with an archived badge, and N matches the total number of archived environments, scans, and finding groups for this repository.
• After unarchive / Unarchive env, the badge is gone and the item is back in the default view — nothing was lost.

Troubleshooting

• No archive buttons are shown. Your account lacks the archive permission for this repository — see Roles and permissions.
• “not an env owner” / “not the hunt owner”. You hold the capability but did not launch the work in question. Ask the person who launched it, the organization owner, or a site admin.
• Something “disappeared”. It was probably archived — possibly along with its parent environment. Select Include archived (N) to reveal it, then unarchive to restore.
• An archived finding came back in a new scan. Expected: archiving hides display history, it does not influence future scans. To suppress a false positive going forward, reject it during review or pin an accepted-behavior card — see Acknowledge true positives or reject false positives and Maintain repository knowledge.

Next step

Put the repository on a cadence so fresh results keep arriving — Schedule recurring scans. Related reading: Monitor environments and scan jobs.