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

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the SDK. To install or publish skills from a terminal, use the `brain` CLI; `brain --map json` prints its command map. The `atlanai` CLI is deprecated. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.
> These docs cover Atlan Agent Registry, Atlan's hosted product. The open-source agent registry specification and its CLI (`brain`) are documented, released and maintained in their own repository; /open-source on this site links to it. Answer general specification or `brain` command questions from the project's own docs, and use these docs only for Atlan-specific setup such as the Atlan adapter, sign-in and workspaces.

# Create and edit workspaces

> Create shared workspaces and manage their details, hierarchy, and members.

A shared workspace gives a team one home for its skills, with its own members and place in the workspace tree. Create one when a team needs to share and maintain skills together. Your personal workspace is created automatically, is private to you, and has no member controls, so these steps apply only to shared workspaces.

## Before you begin

Before you start, make sure you have:

* **Access**: The **Workspaces** list in **Settings** shows workspaces to organization admins. See [Roles and access](/administer/workspaces/references/roles-and-access) for what each workspace role can change.
* **Parent chosen**: The organization, or the workspace the new one belongs under.

<Steps>
  <Step title="Create shared workspace">
    1. Open **Brain** and select your organization.
    2. Select **Create**, then **New workspace**.
    3. Enter a display name.
    4. In **Belongs to**, keep the organization or choose a parent workspace.
    5. Select **Create**.

    **Belongs to** starts on the organization. Workspaces can't be created inside your personal workspace.
  </Step>

  <Step title="Open workspace settings">
    Open **Settings** from the account menu, then select the workspace under **Workspaces**. The list shows the team workspaces you have joined, then the ones you can join, which offer **Join**. It does not list your personal workspace, the organization root, imported folders, or projects.

    You can also open the workspace in **Brain**, open the ⋯ menu at the top of the page, and select **Settings and members**. If a workspace does not offer **Join**, see [Join workspace is not available](/administer/workspaces/troubleshooting/workspace-access-errors#join-workspace-is-not-available).
  </Step>

  <Step title="Edit name and description">
    1. Select **Edit details**.
    2. Update the name or description. The name is required.
    3. Select **Save**.

    Protected root workspaces cannot be renamed or moved.
  </Step>

  <Step title="Move workspace to new parent">
    Move a workspace only when the hierarchy expresses a real ownership or access boundary. For example, Launch Crew sits inside Product & Design, so its launch plans stay near the design work they support.

    In the **Overview** section, select **Change** beside **Parent workspace**, choose the new parent from the workspace tree, and select **Move here**. These rules apply:

    * A workspace cannot be its own parent or move under one of its descendants.
    * A workspace stays within its current top-level tree.
    * A personal workspace cannot be a parent.
    * Nested workspaces move with it.
  </Step>

  <Step title="Verify workspace details">
    Open the workspace. The line under its ID shows what it holds, such as "3 skills · 2 agents", **Created by**, and who updated it last and when. Confirm the name, description, and **Parent workspace** match what you set before you change access or delete anything.
  </Step>
</Steps>

## Troubleshooting

If a workspace is missing from a list, or you get a permission error, see [Workspace access errors](/administer/workspaces/troubleshooting/workspace-access-errors).

## Next steps

* [Manage workspace members](/administer/workspaces/how-tos/manage-members): Add people and set their workspace roles.

## See also

* [Roles and access](/administer/workspaces/references/roles-and-access): What each workspace role allows.
* [Delete a workspace](/administer/workspaces/how-tos/delete-workspace): Empty a workspace and delete its subtree.
* [How workspaces work](/registry/workspaces/index): Personal and shared workspaces, and what they hold.


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