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

# Create and manage workspaces

> Create Oplane workspaces, find and organise them on the Workspaces page, and track requirement progress inside each one.

This page covers creating workspaces, managing them from the Workspaces page, and tracking requirement progress. For what the kinds of workspace are and how they behave, see [Workspaces](/docs/how-it-works/workspaces).

## Creating a workspace

Click **+ Workspace** in the top right corner to open the New Workspace page. Every workspace is created through the same flow:

1. **Name and description**: Enter a name (e.g. your project name) and an optional description.
2. **Sources**: Optionally connect a Git repository. Leave this section empty to run threat modeling locally with your coding agent via [MCP](/docs/find/mcp). See [Kinds of workspace](/docs/how-it-works/workspaces#kinds-of-workspace).
3. **Access**: Add team members by name or email and set general access (restricted or open to the organisation).
4. Click **Create**.

## Managing workspaces

From the Workspaces page you can star a workspace to pin it at the top of your list, search across all workspaces by name, switch between the grid and list layouts, and filter down to just your starred workspaces.

Each workspace card shows the number of threat models and member count at a glance. Repo-connected workspaces display a git-provider indicator with a **Connected** label; it turns into a red **Access disabled** state when Oplane loses access to the repository. Your personal workspace is marked with a **Yours** chip.

## Tracking requirement progress

Inside a workspace, each threat model card shows requirement progress at a glance. A compact chip per severity shows how many requirements are still left to fix at that level (those marked Not Implemented or Partially Implemented), next to a circular ring showing overall completion percentage. Requirements that haven't been reviewed yet are grouped into a single neutral "unreviewed" chip. Hover over the ring to see resolved/total counts for each severity. Once every requirement is resolved, the chips disappear and the ring turns green.

See [Statuses and severity](/docs/reference/statuses-and-severity) for what each severity level and requirement status means.

## Read next

* [Roles and permissions](/docs/administration/roles#workspace-permissions), for who can do what in a workspace.


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