> For the complete documentation index, see [llms.txt](https://docs.changeup.com/app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.changeup.com/app/changeup-dms/widget-setup/test-and-live-environments.md).
# Test and Live Environments
The DMS has two environments where donation widgets are created and managed: Test and Live. Set the toggle to the required environment when creating widgets for integration testing or building production-ready widgets.
Environment switch in different settings.
### Sandbox Development
Widgets created under the Test Mode will only report data to Test reports and cannot, under any circumstances, be used on a production website. They will not work, and no donations will be collected.
### Production Applications
Switch to Live once ready to deploy production widgets that will record donations and charities and collect the data for [analytics](/app/changeup-dms/reporting.md).
---
# 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.changeup.com/app/changeup-dms/widget-setup/test-and-live-environments.md?ask=&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.
