> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/workspace-settings-and-administration/team-users-and-access/access-a-rhythms-sandbox-workspace.md).

# Access a Rhythms sandbox workspace

For users with access to more than one workspace, such as a sandbox.

## Who this applies to

This applies only to users who have access to more than one workspace, such as admins or power users who were given a sandbox in addition to their production workspace. If you have access to only one workspace, you will not see workspace switcher options.

## How to switch to your sandbox

1. Sign in to Rhythms.
2. Click the workspace name or workspace switcher dropdown in the top left corner of the app.
3. Select the sandbox workspace from the list.
4. Confirm that the workspace name in the top left now shows your sandbox workspace.

## Switching back

To return to your main workspace, open the same workspace switcher dropdown in the top left corner and select your main workspace.

## Things to know

* Sandbox data is separate from your production workspace.
* Changes you make in the sandbox do not affect production.
* If you expect a sandbox workspace but do not see it in the dropdown, contact your Rhythms admin or account contact.


---

# 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://help.rhythms.ai/workspace-settings-and-administration/team-users-and-access/access-a-rhythms-sandbox-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.
