> For the complete documentation index, see [llms.txt](https://docs.getdot.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getdot.ai/train-dot/workspaces.md).

# Workspaces

Separate environments for different teams

Workspaces are isolated environments within your organization—separate users, data connections, and permissions, but shared billing.

**Use cases**: Team separation (Sales vs Finance), client isolation, regional data separation, testing environments.

### Creating a Workspace

*Org admins only*

1. **Settings → Workspaces → Create Workspace**
2. Enter a name, optionally copy data from another workspace
3. Done

<figure><img src="https://3709841693-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCeRlmJf2y704TpjpubE1%2Fuploads%2Fgit-blob-a9b327177c440ae7516814eb17912f7f92513ffe%2Fworkspace-create-dialog.png?alt=media" alt=""><figcaption><p>Create a new workspace with optional data copying</p></figcaption></figure>

Limits: 10 workspaces (free) / 200 (unlimited).

### Switching Workspaces

Click your **workspace name** (bottom-left) → select another workspace.

<figure><img src="https://3709841693-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCeRlmJf2y704TpjpubE1%2Fuploads%2Fgit-blob-ca6e1adb660cbbad313e43d8c29ec9751c815d3c%2Fworkspace-switcher.png?alt=media" alt=""><figcaption><p>Switch between workspaces from the sidebar</p></figcaption></figure>

You can set a default workspace in your user settings.

### Adding Users

1. **Settings → Workspaces** → find workspace → **Manage Users**
2. Enter email, select role (User/Admin), click Add

New users invited to a workspace can only see that workspace. Admins can grant full org access later.

### Slack & Teams Routing

Route specific channels to workspaces. See [Channel Routing](/integrations/slack-and-teams/channel-routing.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.getdot.ai/train-dot/workspaces.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.