> ## Documentation Index
> Fetch the complete documentation index at: https://docs.launchsafe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a Workspace

> Set up a LaunchSafe workspace to organize targets, scans, findings, team members with role-based access, integrations, and billing in one place.

A workspace is the top-level organizational unit in LaunchSafe. Everything — targets, scans, findings, reports, integrations, billing, and team members — belongs to a workspace. Think of it as your company or project's security operations center.

## Creating your first workspace

During onboarding, you'll set up your first workspace in three steps:

<Steps>
  <Step title="Name your workspace">
    Choose a name that identifies your organization or project. This name is visible to all workspace members and appears in reports.

    **Good examples:** "Acme Corp", "My SaaS App", "Backend Services"

    Workspace names must be 3–60 characters. You can change the name later in Settings.
  </Step>

  <Step title="Choose your team type">
    Select how your team is structured:

    * **Solo** — you're the only person using LaunchSafe. The workspace is configured for individual use with streamlined defaults.
    * **Team** — you'll be inviting teammates. The workspace includes collaboration features like member management, role-based access, and shared notifications.

    This choice affects default notification settings and onboarding flow but can be changed later.
  </Step>

  <Step title="Invite team members (optional)">
    If you selected "Team", you can invite colleagues by email address. Each invited member receives an email with a link to join your workspace.

    Invited members get full access to all scans, findings, and reports in the workspace. Member management and role-based access control are available in Settings after onboarding.
  </Step>
</Steps>

## Workspace configuration

After creation, your workspace can be configured from **Settings** in the sidebar:

### General settings

| Setting            | Description                                                                                            |
| ------------------ | ------------------------------------------------------------------------------------------------------ |
| **Name**           | Your workspace display name. Appears in the sidebar, reports, and email notifications.                 |
| **Production URL** | Your live application URL. Used as the default target for black-box scans and displayed in reports.    |
| **Staging URL**    | Your staging/test environment URL. Useful for running DAST scans against a non-production environment. |

### Notification settings

| Setting                       | Description                                                                                                             |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Email on scan complete**    | Send an email to workspace members when a scan finishes. Includes a severity summary and link to results.               |
| **Email on critical finding** | Send an immediate email when a critical-severity vulnerability is discovered — even before the scan completes.          |
| **Notification email**        | Override the default email recipient for notifications. Useful for routing alerts to a security team distribution list. |
| **Slack webhook URL**         | Post notifications to a Slack channel via webhook. See [Slack Integration](/integrations/slack) for details.            |

### Member management

Workspaces support team collaboration with role-based access control. Admins and owners can:

* **Invite new members** — send email invitations to colleagues
* **Remove members** — revoke access for team members who leave
* **Change roles** — assign each member the level of access they need

Owners can additionally **transfer ownership** of the workspace to another member.

### Roles and permissions

Every member has one of four roles. Each role includes everything the role below it can do:

| Role       | Can do                                                                                                                                               |
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Viewer** | View scans, findings, reports, analytics, and notifications                                                                                          |
| **Member** | Everything a Viewer can do, plus run scans, upload code, update findings, create tickets, apply auto-fixes, share reports, and manage scan schedules |
| **Admin**  | Everything a Member can do, plus delete scans, manage targets, domains, repositories, integrations, and invite or remove members                     |
| **Owner**  | Full access, including billing and deleting or transferring the workspace                                                                            |

<Info>
  Each workspace has one owner by default — the person who created it. Ownership can be transferred to another member at any time.
</Info>

## Multiple workspaces

You can create and manage multiple workspaces for different projects, clients, or environments. Common patterns:

| Pattern             | Example                                               |
| ------------------- | ----------------------------------------------------- |
| **Per-product**     | "Main App", "Mobile API", "Admin Portal"              |
| **Per-client**      | "Client: Acme Corp", "Client: Globex Inc"             |
| **Per-environment** | "Production Scans", "Staging Scans", "CI/CD Pipeline" |

### Switching workspaces

Click your profile icon in the bottom-left of the sidebar → **Switch organization** → select the workspace you want to switch to. Your dashboard, scans, and findings update to reflect the selected workspace.

Each workspace has its own:

* Targets and scan history
* Findings and reports
* Integrations (GitHub, Slack, Jira, Linear)
* Billing and subscription
* Team members and permissions

## Workspace data isolation

Workspaces are completely isolated from each other:

* Members of one workspace cannot see data from another workspace (even if they belong to both)
* Integrations and credentials are scoped to a single workspace
* Integrations are configured per-workspace
* Billing is separate per-workspace

This isolation ensures that multi-tenant usage (e.g., consultancies managing multiple clients) maintains strict data separation.

## Deleting a workspace

To delete a workspace:

1. Go to **Settings** → **Danger Zone**
2. Cancel any active subscription first (required)
3. Type `DELETE` to confirm
4. Click **Delete Workspace**

<Warning>
  Deleting a workspace permanently removes all targets, scans, findings, reports, and integration configurations. This action cannot be undone. Export any reports you need before deleting.
</Warning>

## Next step

<Card title="Add a Target" icon="crosshairs" href="/getting-started/add-target">
  Connect your code or application for security testing.
</Card>