Skip to main content
Projects group related repositories together, allowing you to organize security scanning by team, application, or any structure that fits your workflow.

​
Creating a Project

  1. Click “New Project” in the sidebar
  2. Enter a project name
  3. Click “Create”

​
Project Structure

Each project contains:
SectionDescription
RepositoriesConnected code repositories
IssuesSecurity findings across all repos
Pull RequestsPR-specific scan results
LearningsFalse positive rules
SettingsAPI keys, integrations, team access

​
Managing Projects

​
Switch Projects

Use the project dropdown in the sidebar to switch between projects.

​
Rename a Project

  1. Go to project Settings
  2. Click “General”
  3. Update the project name
  4. Click “Save”

​
Delete a Project

  1. Go to project Settings
  2. Scroll to “Danger Zone”
  3. Click “Delete Project”
  4. Confirm deletion
Deleting a project permanently removes all repositories, issues, and learnings associated with it.

​
Project Organization

​
By Application

Create one project per application: 
├── Web App
│   ├── frontend repo
│   └── backend repo
├── Mobile App
│   └── mobile repo
└── Admin Dashboard
    └── admin repo

​
By Team

Organize by team ownership: 
├── Team Alpha
│   ├── service-a
│   └── service-b
├── Team Beta
│   └── service-c

​
By Environment

Separate by deployment environment: 
├── Production
│   └── prod repos
├── Staging
│   └── staging repos

​
Project Settings

​
API Keys

Each project has its own API keys:
  1. Go to Settings → API Keys
  2. Create keys for CI/CD or CLI access
  3. Keys are scoped to this project only
See API Keys for details.

​
Team Members

Manage who has access:
  1. Go to Settings → Team
  2. Invite members by email
  3. Assign roles (Admin, Member, Viewer)
See Team Members for details.

​
Integrations

Configure project-specific integrations:
  1. Go to Settings → Integrations
  2. Connect GitHub for this project
  3. Each project can have different GitHub orgs

​
Project Metrics

The project dashboard shows:
  • Total Issues - Open security findings
  • Critical/High - Priority issues count
  • Repositories - Connected repos count
  • Recent Activity - Latest scans and changes

​
Best Practices

​
Naming Conventions

Use clear, consistent names:
  • customer-portal not cp
  • payment-service not svc1

​
Repository Grouping

Group repos that:
  • Deploy together
  • Share the same security context
  • Are managed by the same team

​
Learnings Scope

Remember that learnings are project-scoped:
  • A learning in Project A doesn’t affect Project B
  • Consider this when organizing repos

Repositories

Add repos to projects

API Keys

Manage project API keys

Team Members

Manage access

Dashboard Overview

Navigate the dashboard