> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/device-management/managing-a-workspace/general-settings/actions.md).

# Actions

Delete a workspace.

The **Actions** section at the bottom of the [General settings](/device-management/managing-a-workspace/general-settings.md) page holds the destructive operations for a workspace.

## Delete workspace

*Delete Workspace* removes the workspace from your organization.

{% hint style="danger" %}
Deleting a workspace cannot be undone. It removes the devices, device data, integrations, data flows, and rules that belong to it.

Before deleting, make sure anything you still need has been sent somewhere outside akenza, by exporting device data via the UI or read out through the [REST API](/reference/api-documentation.md).
{% endhint %}

Deleting a workspace requires the **Workspace Admin** role. Dashboards are managed at organization level, so they are not part of the workspace, but any component that pointed at a deleted workspace's devices no longer has data to show.


---

# 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.akenza.io/device-management/managing-a-workspace/general-settings/actions.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.
