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

# Workspace switching

<figure><img src="/files/YnSZOF4y15DHdKoUccaD" alt=""><figcaption></figcaption></figure>

You can easily switch between all the workspaces you are a member of by using the workspace switcher. To reveal the switcher, hover over the sidebar to expand it, and then click on the name of the workspace that is listed.

This will open up the workspace switcher, where you can easily select any of the other workspaces you are in and switch to it. From this view, you'll also be able to see and accept any pending invites.

If you're using the same email address for other organizations, you will also see these organization(s) and workspace(s) listed in the switcher.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.shippercrm.com/teams-and-agencies/workspace-switching.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.