Projects group related repositories together, allowing you to organize security scanning by team, application, or any structure that fits your workflow.
Creating a Project
- Click “New Project” in the sidebar
- Enter a project name
- Click “Create”
Project Structure
Each project contains:
| Section | Description |
|---|
| Repositories | Connected code repositories |
| Issues | Security findings across all repos |
| Pull Requests | PR-specific scan results |
| Learnings | False positive rules |
| Settings | API keys, integrations, team access |
Managing Projects
Switch Projects
Use the project dropdown in the sidebar to switch between projects.
Rename a Project
- Go to project Settings
- Click “General”
- Update the project name
- Click “Save”
Delete a Project
- Go to project Settings
- Scroll to “Danger Zone”
- Click “Delete Project”
- 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:
- Go to Settings → API Keys
- Create keys for CI/CD or CLI access
- Keys are scoped to this project only
See API Keys for details.
Team Members
Manage who has access:
- Go to Settings → Team
- Invite members by email
- Assign roles (Admin, Member, Viewer)
See Team Members for details.
Integrations
Configure project-specific integrations:
- Go to Settings → Integrations
- Connect GitHub for this project
- 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 cppayment-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
Related Pages
