> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/workspace/create-and-change-workspace.md).

# Create & change workspace

Each workspace is completely independent, with its own dashboard, billing, and team members. 

(e.g. if you are an agency with multiple clients or a company with separate departments/teams, you may need to create different Guideflow workspaces.)

### Create a new workspace

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/lpnvwlsjrv>" %}

* To create a new workspace, click on your profile icon at the bottom left of your dashboard.&#x20;
* Click on "New workspace".
* And type its name in the popup.

### Change workspace

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/1pz2g0uvp8>" %}

* To switch between your existing workspaces, click on your profile icon at the bottom left of your dashboard&#x20;
* And click on the workspace you want to switch to.

{% hint style="info" %}
If you want to join an existing workspace, ask one of its administrators to invite you and join the workspace via the link that will be emailed to you.
{% endhint %}


---

# 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.guideflow.com/help/workspace/create-and-change-workspace.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.