> For the complete documentation index, see [llms.txt](https://docs.instruqt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.instruqt.com/resources/faq/using-cleanup-scripts-in-saas-and-cloud-environments.md).

# Using Cleanup Scripts in SaaS and Cloud Environments

Cleanup scripts are a useful tool for managing and resetting SaaS software and Cloud accounts after they have been used in a sandbox environment.

## Examples of Cleanup Script Usage

1. **SaaS Software**: If you are using your own SaaS software that requires cleanup after the sandbox is deprovisioned, a cleanup script can be used to run commands against your SaaS environment and reset it back to its default settings.
2. **Cloud Accounts**: If you are using your own Cloud accounts and need to reset them after the sandbox is used, a cleanup script can be a valuable tool.

Please note that all Google-based resources and Cloud accounts provided by Instruqt are automatically cleaned up after the track is complete. This means you do not need to worry about manually resetting these resources.

Remember to always check the specific requirements and settings of your SaaS software and Cloud accounts to ensure that the cleanup script is correctly configured and will not cause any unintended changes or data loss.


---

# 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.instruqt.com/resources/faq/using-cleanup-scripts-in-saas-and-cloud-environments.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.