Skip to main content

​
Overview

Workspaces are isolated environments for organizing security scanning. Each workspace has its own integrations, repositories, members, and settings, completely separate from other workspaces.

​
What lives inside a workspace

  • Integrations: GitHub, GitLab, Jira, Linear
  • Organizations and repositories: synced from your VCS integrations
  • Applications: logical groupings of repositories
  • Scans and vulnerabilities: all security findings
  • Members and roles: who can access what

​
Use cases

  • Business units or departments: Create separate workspaces for engineering, platform, and security teams, each with their own repositories and vulnerability tracking.
  • Client segregation: MSPs and consultancies can create a workspace per client, ensuring complete data isolation between engagements.
  • Environment separation: Separate production and staging environments into different workspaces for clearer insights and access control.

​
Multi-workspace access

  • Single account: one login, multiple workspaces
  • Different roles: you might be an owner in one workspace and a developer in another
  • Central billing: all workspaces under one subscription
  • Easy switching: switch between workspaces from the workspace selector

​
Data isolation

Each workspace has a completely separate database. Data never crosses workspace boundaries.
This architecture is designed to support compliance frameworks including SOC 2, ISO 27001, and GDPR. See Trust & Security for current certification status.