Skip to main content
Workspaces are available on all paid plans. Accounts with the Free Edition have access to a single default workspace only.
Workspaces group related assets, targets, scans, findings, and attack surface data into a separate context for each project or client. When you create an account, a default workspace called My Workspace is automatically created. On paid plans, you can create additional workspaces and share them with team members.

What workspaces contain

Each workspace includes:
ItemDescription
Assets and targetsThe targets you add for security testing
ScansAll scan history for this workspace
Scheduled scansRecurring scans configured for workspace targets
FindingsVulnerabilities discovered in workspace scans
Attack surface dataTechnology fingerprints and discovered hosts
Notification settingsWorkspace-specific alert configurations
HandlersXSS Exploiter and HTTP Request Logger data scoped to the workspace
You can assign a VPN profile to a workspace. When assigned, all scans in that workspace route through your internal network. Learn more about VPN profiles.

Creating a workspace

Go to the Workspaces page, or use the sidebar dropdown:
1

Open the workspace dropdown

Click the workspace dropdown at the top of the sidebar.
2

Create workspace

Select Create workspace.
3

Enter details

Enter a name and optional description.
4

Confirm

Click Create.

Switching workspaces

1

Open the workspace dropdown

Click the workspace dropdown at the top of the sidebar.
2

Select a workspace

Select the workspace you want to switch to.
3

View workspace contents

The interface updates to show that workspace’s assets, scans, and findings.

Organization strategies

StrategyGood forExample
By clientConsulting firms and MSPsOne workspace per client to keep data separate
By projectInternal security teamsWorkspaces for initiatives like “Q4 Assessment” or “New Product Launch”
By environmentDevSecOps teamsSeparate workspaces for Development, Staging, and Production

Sharing workspaces

Share workspaces with team members on your account. When sharing, you grant one of the following access levels:
Access levelWhat they can do
No accessCannot view or interact with the workspace
ViewSee assets, scans, and findings. Cannot start scans or modify anything.
EditFull access to start scans, manage assets, and work with findings. Cannot delete the workspace.

How sharing works

  1. The workspace owner shares a workspace with selected team members
  2. Team members see the shared workspace in their workspace list
  3. Team members can switch to the shared workspace and work according to their permissions
  4. Scans started by team members appear in the shared workspace, visible to all members with access
Use workspace sharing to collaborate on client engagements. Share a client workspace with your team so everyone can see findings and contribute to the assessment.

For workspace owners

  • Share workspaces from the workspace page or from Settings > Team > Sharing
  • Choose which workspaces to share and with which team members
  • Set appropriate access levels for each team member
  • Revoke access at any time by removing sharing permissions

For team members

  • Shared workspaces appear in your workspace dropdown
  • Your access level determines what actions you can take
  • Switch between your own workspaces and shared workspaces freely
  • Scans you start in a shared workspace are visible to all members with access

Deleting a workspace

Go to the Workspaces page, select one or more workspaces, and click Delete. You’ll be asked what to do with the contents:
  • Move assets: Transfer all assets and their data to your default workspace
  • Delete everything: Permanently remove all assets, scans, and findings
Deleting a workspace cannot be undone. If you choose to delete everything, all associated scan history and findings are permanently removed.

Best practices

Name workspaces clearly so you and your team can quickly identify them. Include client names, project codes, or environment indicators.
Configure notification settings per workspace to get alerts relevant to each project. This prevents notification overload from unrelated scans.
If you’re scanning internal networks, assign the appropriate VPN profile to the workspace so all team members use the correct network path.
Periodically audit who has access to which workspaces and what access levels they have, especially after team changes or project completions.