> 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/rdm/getting-started/workspaces/offline-mode/devolutions-cloud-offline-mode.md).

# Devolutions Cloud offline mode

Enable offline mode for a Devolutions Cloud workspace in Remote Desktop Manager by allowing user accounts to go offline and reviewing workspace information.

Follow the steps to lean how to enable [offline mode](/rdm/getting-started/workspaces/offline-mode.md) for a [Devolutions Cloud workspace](/rdm/getting-started/workspaces/workspace-types/native-workspaces/devolutions-cloud.md).

#### User account offline mode setting

To enable a user account to use offline mode, go to ***Administration*** – ***Users*** – ***Edit*** and click ***Allow offline***.

#### Workspace information

To have a overview of the workspace configuration, open the [workspace information](/rdm/ribbon-menu-bar/file/my-workspace-information.md) by going to ***File - My workspace information*** in Remote Desktop Manager.

#### Going offline

Remote Desktop Manager will prompt for offline mode when the application is unable to reach the workspace. The offline mode can also be toggled manually via ***File*** – ***Go offline*** or by clicking the ***Go offline*** button located in the bottom pane (Windows only).


---

# 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/rdm/getting-started/workspaces/offline-mode/devolutions-cloud-offline-mode.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.