> 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/cli/guides/connect.md).

# Connect to your workspaces

Save Devolutions Cloud, Devolutions Server, and local profile workspaces as Devolutions CLI contexts, then switch between them.

Before Devolutions CLI can read a secret, it needs to know where your secrets live. `devo login` saves a workspace as a **context**, a name you choose, and makes it the current one. You do it once per workspace, then switch between contexts as you need.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Sign in to Devolutions Cloud</strong></td><td>Sign in with your browser, or with an application key for scripts and pipelines.</td><td><a href="/cli/guides/connect/devolutions-cloud.md">Sign in to Devolutions Cloud</a></td></tr><tr><td><strong>Sign in to Devolutions Server</strong></td><td>Sign in with your browser, an API key, a username and password, or Windows authentication.</td><td><a href="/cli/guides/connect/devolutions-server.md">Sign in to Devolutions Server</a></td></tr><tr><td><strong>Use a local Devolutions Remote Desktop Manager profile</strong></td><td>Point Devolutions CLI at a profile folder on your computer. No sign-in needed.</td><td><a href="/cli/guides/connect/local-profile.md">Use a local Devolutions Remote Desktop Manager profile</a></td></tr><tr><td><strong>Switch between workspaces</strong></td><td>List your contexts, change the current one, or use another workspace for a single command.</td><td><a href="/cli/guides/connect/switch-workspaces.md">Switch between workspaces</a></td></tr></tbody></table>

Not sure which workspace type does what? See [Compare workspace types](/cli/guides/understand/workspace-types.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.devolutions.net/cli/guides/connect.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.