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

# Workspaces

Manage and delete Devolutions Cloud workspace instances associated with your Devolutions Account from the Products section of Devolutions Portal.

The ***Workspaces*** section provides access to the different Devolutions products associated with the user's account:

* ***Devolutions Cloud*** is a highly-secure, flexible and easy-to-use cloud based password management solution for businesses who need to share passwords and credentials within their organization. Individual users wanting to secure personal passwords in a secure vault can do so for free.

### Deleting Devolutions Cloud

To delete an instance of Devolutions Cloud, navigate to the ***Product*** section of the [Devolutions Portal](https://portal.devolutions.com/), then click on the vertical ellipsis button next to the Devolutions Cloud instance to delete and click ***Delete***.

{% hint style="warning" %}
For Devolutions Cloud, only the workspace [owner](https://docs.devolutions.net/cloud/web-interface/administration/management/users/devolutions-cloud-ownership) can delete it.
{% endhint %}


---

# 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.devolutions.net/portal/products.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.