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

# Workspace

> Understand workspaces in OASM - isolated tenants for multi-tenant attack surface management

A **Workspace** is the core organizational unit in OASM and the foundation of its multi-tenant architecture. Each workspace is an isolated tenant with its own targets, assets, users, and settings. Everything created inside a workspace — discovered assets, scan results, vulnerabilities, workflows, and configuration — stays inside that workspace and is never visible to users of another workspace.

This strict isolation allows a single OASM instance to serve multiple teams, clients, or environments (for example, production and staging) on the same platform without any data mixing.

> [!NOTE]
>
> You need to join at least one workspace before you can use OASM features.

## Key concepts

### Workspace cards

Workspaces are presented as cards on the workspace overview. Each card shows the workspace **status** (for example, **Active**), the number of **members**, and the number of **targets** registered in that workspace. The card acts as a quick health summary of the tenant before you open it.

### Workspace switcher

The workspace switcher, located in the top area of the console, lets you move between all workspaces you can access. Switching changes the entire context — targets, assets, members, API keys, and audit log — because each workspace is fully independent.

### Workspace owner

The user who creates a workspace becomes its **Owner**. Owners hold all permissions within the workspace, including the ability to manage members, configuration, and the workspace itself. Ownership cannot be transferred from the console.

## Create a workspace

**1. Open the workspace list**

From the console, navigate to the workspace overview or open the workspace switcher.

**2. Click New workspace**

The **New workspace** button opens the creation form.

**3. Enter a name**

Provide a unique workspace name. Use a descriptive name such as the team, client, or environment it represents.

**4. Add a description (optional)**

Add context about the workspace, for example the project purpose or environment like production or staging.

**5. Create the workspace**

Submit the form. The creating user becomes the workspace **Owner** and is granted all permissions.

## Manage workspace settings

Workspace settings are available under **Settings → General** and are organized into two sections.

### Information

The **Information** section contains the workspace **Name** and **Description**. Update either field and click **Save** — changes apply immediately and are reflected across the entire workspace, including the workspace switcher and workspace cards.

### Configs

The **Configs** section provides two switches that control automatic behavior:

* **Asset discovery** — enables automatic discovery of assets for the workspace's targets.
* **Auto enable assets** — automatically enables newly discovered assets for further scanning and processing.

Toggle either switch and click **Save** to apply the change.

> **How do the Configs switches work together?**
>
> **Asset discovery** controls whether discovery jobs are scheduled for targets. **Auto enable assets** controls what happens to the results: when enabled, newly discovered assets are enabled automatically instead of waiting for manual approval. The two switches are independent — you can discover assets without auto-enabling them.

## Delete a workspace

**1. Open Settings → General**

Navigate to the workspace settings.

**2. Scroll to the Danger Zone**

The **Danger Zone** section is at the bottom of the settings page.

**3. Click Delete Workspace**

Confirm the deletion when prompted.

> [!CAUTION]
>
> Deleting a workspace permanently removes all of its data, including targets, assets, and vulnerability data. This action is **irreversible** — there is no recovery path. Export anything you need before deleting.

## Workspace settings reference

| Setting | Options | Description |
| - | - | - |
| Name | Free text | Display name of the workspace, shown in cards and the switcher |
| Description | Free text | Optional context about the workspace |
| Asset discovery | On / Off | Enables automatic asset discovery for workspace targets |
| Auto enable assets | On / Off | Automatically enables newly discovered assets |
| Delete Workspace | Button | Irreversibly deletes the workspace and all associated data |

## Best practices

* Create a separate workspace for each environment or client to keep data strictly isolated.
* Use the workspace switcher to verify you are operating in the correct tenant before making changes.
* Delegate day-to-day access through [permission groups](/members) instead of granting ownership to every collaborator.
* Keep the number of workspace owners minimal — owners can delete the workspace and its data.
* Review members and invitations regularly; remove members who no longer need access.

## Related

> **[Members](/members)**
>
> Manage members, invitations, and permission groups within a workspace

> **[Users and roles](/users-and-role)**
>
> Manage user accounts and platform-wide roles

> **[API keys](/api-keys)**
>
> Manage the workspace API key for programmatic access


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.