> ## 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.
# Workspaces
> Create shared workspaces and manage their details, hierarchy, and members.
Create shared workspaces from your organization in Brain. After creation, use
Settings to update their details, hierarchy, and membership.
Atlan creates your personal workspace automatically. It is private to you and
has no member-management controls. The procedures on this page apply to shared
workspaces.
## Open workspace settings
1. Open **Settings** from the Atlan sidebar.
2. Under **Workspaces**, select the workspace you want to manage.
The Workspaces group lists the team workspaces you have joined. It does not list
your personal workspace, the organization root, imported folders, or projects.
You can also open a workspace's action menu in the Brain sidebar and select
**Settings and members**.
## Create a shared workspace
1. Open **Brain** and select your organization.
2. Select **New**, then **New workspace**.
3. Enter a display name.
4. Add a description that tells people what belongs in the workspace.
5. Select **Create**.
Atlan creates the workspace in the organization's default location. Open its
settings to choose a different parent.
## Edit workspace details
1. Open the workspace in **Settings**.
2. Open **Workspace actions**.
3. Select **Edit details**.
4. Update the name or description.
5. Select **Save**.
The name is required. Protected root workspaces cannot be renamed or moved.
## Organize the workspace hierarchy
A sub-workspace sits inside another workspace. Use sub-workspaces when a team
needs a focused area without creating another top-level branch. For example,
Launch Crew sits inside Product & Design, so its launch plans stay near the
design work they support.
Select **Set parent** when no parent is set, or **Move** when the workspace is
already nested. Choose the new parent from the workspace tree.
New workspaces are created in a default location. Move a workspace only when a
team needs that hierarchy to express a real ownership or access boundary.
Atlan applies these rules when moving a workspace:
* 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 used as a parent.
* Moving a workspace moves its nested workspaces with it.
## Check workspace details
The details card shows the workspace owner, creation date, skill count, and
member count. Use these values to confirm that you opened the intended
workspace before changing access or deleting it.
A workspace can show a linked repository when it came from a registered
source. Adding a repository manually is not available yet. The **Connect**
action remains disabled.
## Next steps
Add people and update their workspace roles.
See what each workspace role allows.
Empty a workspace and delete its subtree.