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

# Organizations and workspace switching

Switch organizations to work with the projects and settings of another team. Each organization has its own members, roles, and resources.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FZsZnHRbN0UkkUQeQllvi%2FG087.mp4?alt=media&token=0ece48c2-816a-4ab9-9d13-1e408a1476c6>" %}

## Before you start

Use an account that already belongs to the destination organization. If it is missing, confirm you accepted the invitation using [Invitations and joining an organization](https://docs.stackai.com/guides-and-quickstarts/workspace-and-discovery/invitations-and-joining-an-organization.md) or ask the organization administrator to check your membership; switching cannot grant access to a new organization.

## Switch to an organization

Open Settings → Organizations and locate the organization you need.

![Organizations list and Current badge](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/gLtnRVUzTLEgMv8TE1Es/assets/g087-g087-01-list.png)

Check its name, identifier, plan, and Current badge before switching.

Open the destination organization's row menu and select Switch.

![Destination organization Switch menu](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/RZ36IOt7yPiLOhEF8tgW/assets/g087-g087-02-menu.png)

Use the organization name to distinguish the destination from your current workspace.

Return to the dashboard and review the selected organization and its projects.

![Dashboard after switching organization](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/pVI2nYak6efjRWjvx4XT/assets/g087-g087-03-workspace.png)

Confirm the workspace before opening or editing a project.

## Check your role

Open Settings → Members to check your role in that organization.

![Member role in the selected organization](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/n3nFPxSJ6LXtA66rvoCq/assets/g087-g087-04-membership.png)

Your permissions can differ between organizations.

## Switch again when needed

Use the organization switcher when you need another workspace.

![Organization switcher](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/kj5cnC9Imw1gJ45uCr1Z/assets/g087-g087-05-return.png)

Confirm the expected organization and projects after each switch.

## Important behavior

Your role and project access can differ between organizations. Confirm the active organization before changing its settings.


---

# 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.stackai.com/guides-and-quickstarts/organization-administration/organizations-and-workspace-switching.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.
