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

# Workspaces

> Group databases, manage access and scope integrations to a workspace.

Choose a workspace from the selector above **Operate** in the sidebar. Every installation starts with **Default**, which is shared by all team members and cannot be deleted. Existing databases belong to Default after an upgrade.

## Create a workspace

Admins can choose **Create Workspace** in the selector and enter a name and description. The creating admin becomes its first member. Other admins cannot open the workspace unless they are added to it.

## Manage access

Open **Settings → Workspace Settings** for the selected workspace. **General** edits its name and description. Default shows only **API Keys** in its workspace settings menu. **Manage Access** adds or removes existing team members immediately; there is no invitation or separate workspace role.

Members retain their team-wide Admin, Member or Viewer role. An admin who belongs to the workspace can manage access, including removing themselves. Members and viewers cannot leave or change its membership. Removing someone from the team also removes their workspace memberships.

All team admins can open **Team Settings → Workspaces** to inspect the workspace directory. Choose **View members** to open a read-only member table. This directory does not grant access to workspace data.

## Workspace API keys

Admins with access to a workspace can create, rotate and revoke its API keys. Open **Workspace Settings → API Keys** for either Default or another workspace. A key can access only its own workspace, within its configured permissions. It does not grant team or account administration.

Existing team API keys are revoked by the workspace upgrade and no longer work. Create replacement workspace keys and update your integrations. Personal keys and OAuth retain the user's current team role and workspace memberships.

## API and MCP scope

Use `getContext` or `rootset_get_context` to discover the organisation, then `listWorkspaces` or `rootset_list_workspaces` to discover accessible workspace IDs. Every database, table, record, job, artifact, table-preference operation requires an explicit `workspaceId`, including operations on Default. Supply it in the query string for GET requests and in the JSON input for writes and MCP tools.

Account, team administration and workspace discovery remain team-wide. An inaccessible workspace or a resource from a different workspace returns **Resource not found**.

## Delete a workspace

Use **Workspace Settings → Danger Zone → Delete workspace**. Delete its databases first; the server refuses deletion while any database remains active or is still being deleted. Default cannot be deleted. Deleting an empty workspace also revokes its API keys.


## Related topics

- [Create workspace](https://www.rootset.app/api-reference/createWorkspace.md)
- [Delete workspace](https://www.rootset.app/api-reference/deleteWorkspace.md)
- [Update workspace](https://www.rootset.app/api-reference/updateWorkspace.md)
- [Get workspace](https://www.rootset.app/api-reference/getWorkspace.md)
- [List workspaces](https://www.rootset.app/api-reference/listWorkspaces.md)


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