Skip to content

Clarify coverage of archiving projects #2633

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
armchairlinguist wants to merge 2 commits into
base: main
Choose a base branch
from
+5 −3
Open

Clarify coverage of archiving projects #2633

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e422ffa
Clarify coverage of archiving projects
armchairlinguist May 26, 2026
a46e8d9
Add BBDC, add note about findings
armchairlinguist May 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions docs/deployment/manage-projects.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,16 +14,18 @@ import DeleteAProject from "/src/components/procedure/_delete-a-project.md"

View, sort, and tag your projects through the **Projects** page. Refer to this page to manage and troubleshoot thousands of repositories by identifying scan issues or scans with a high number of findings.

:::note What is a project?
:::note What is a project in Semgrep AppSec Platform?
Copy link
Copy Markdown
Collaborator Author

@armchairlinguist armchairlinguist May 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made this change because several of the SCMs have some concept of "project" as well so it helps avoid ambiguity.

A **project** is a repository, or part of a repository, that you scan through Semgrep AppSec Platform, either using CI or Semgrep Managed Scans. This also includes local CLI scans whose results you have sent for viewing on Semgrep AppSec Platform. A project's scans can be viewed on the **Project details** page, and its findings can be viewed on the individual Semgrep products' **Findings** pages.
:::

The **Projects** page features two tabs:

- The **Scanning** tab lists all projects that have been provisioned or scanned by Semgrep, regardless of whether the project is actively being scanned. If the project's repository has been archived in the source code manager, it is listed under **Not scanning**.
- The **Not scanning** tab lists projects that are associated with [source code manager (SCM) connections that you've added](/deployment/connect-scm), but these projects aren't actively being scanned by Semgrep. The **Not scanning** page also lists projects where you've archived the corresponding GitHub repositories.

- The **Not scanning** tab lists projects that are associated with [source code manager (SCM) connections that you've added](/deployment/connect-scm), but which aren't actively being scanned by Semgrep. For GitHub, GitLab, and Bitbucket Data Center, the **Not scanning** page also lists projects where you've archived the corresponding SCM repositories.

:::note
Findings from a project marked as archived still show in the Semgrep AppSec Platform **Findings** pages.
:::

## Sort projects

Expand Down
Loading