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

# Accessing your sandbox

How to access your system outside the live production environment

The **sandbox** environment is a safe, isolated space where users can explore features, test changes, and practice tasks without affecting real data or the live system. It's commonly used for demonstrations, training, experimentation, and staging for new upcoming versions.

To access your sandbox environment, follow these steps:

1. Visit the Shift iQ website at [www.shiftiq.com](https://www.shiftiq.com/)
2. Click the Sign In link at the top of the page.
3. On the Sign In form, scroll to the bottom of the page.
4. You'll see an information message that reads, "You are signing in to the Production environment."
5. Below this, you'll see links to the other environments available to your organization. Typically, this includes Development and Sandbox.
6. Click the link for the Sandbox environment.
7. Copy the URL from your web browser's address bar.

For example:

<figure><img src="https://1098692194-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEiUUMcDHYlET5DiA1xJY%2Fuploads%2FGsoamjdHyZ1kc1a2tCWv%2Fsignin-environments.png?alt=media&amp;token=912cd1a1-c9ca-45ee-9b4d-c8a88ccb39f3" alt="Signin environments"><figcaption></figcaption></figure>


---

# 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.shiftiq.com/help/sandbox.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.
