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

# How do I delete a workspace (space) on the mobile app?

## Report and Run: Integrate

Before [deleting your Report and Run: Integrate space](/manual/report-and-run-integrate/account-management/delete-your-space.md), you will need to [cancel your subscription](/manual/faq/c167/q555.md).

{% hint style="info" %}
In the cloud version of the app, you will have 7 days to restore your space after scheduling it for deletion. After that, your space will be **permanently** deleted, along with all of its content, including folders, reports, and PDFs. 
{% endhint %}

## Report and Run: Offline

Follow these [steps to delete your space](/manual/report-and-run/content/spaces/delete-space.md).

{% hint style="info" %}
In the offline version of the app, deleting a space will **immediately and** **permanently** delete all content within a space, including folders, reports, and PDFs. 
{% endhint %}

## Related

* [Article: How to cancel a Report and Run: Integrate subscription](/manual/report-and-run-integrate/account-management/cancel-your-subscription.md)
* [Article: How to delete a Report and Run: Integrate space](/manual/report-and-run-integrate/account-management/delete-your-space.md)
* [Article: How to switch spaces in Report and Run: Offline](/manual/report-and-run/content/spaces/switch-spaces.md)
* [Article: How to delete a space in Report and Run: Offline](/manual/report-and-run/content/spaces/delete-space.md)
* [FAQ: How do I create separate workspaces with unique text templates?](/manual/faq/c150/c155/q493.md)
* [FAQ: How do I create, manage, and rename workspaces (spaces) in the app?](/manual/faq/c150/c152/q439.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.reportandrun.com/manual/faq/c150/c152/q443.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.