> 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.md).

# Workspaces

Create and manage Remote Desktop Manager workspaces, switch between multiple local or database workspaces, and configure startup behavior.

{% tabs %}
{% tab title="Windows" %}
Workspaces are at the heart of Remote Desktop Manager, acting as containers for entries.

Use <kbd>Ctrl</kbd>+<kbd>Space</kbd> to easily [search](/rdm/ribbon-menu-bar/view/search.md) through vaults, entries, tabs, and workspaces.

### Settings

A workspace can be a local file or a database (either local or shared). Multiple workspaces can be managed at the same time as seen below.

### Create a workspace

Please consult [Create a workspace](/rdm/getting-started/workspaces/create-a-workspace.md) for more information.

### Multiple workspaces

Multiple workspaces can be configured, but there can only be one workspace active at a time. Switch from one workspace to another by using the workspace drop-down list.

### Startup workspace

You may assign a workspace to open automatically when Remote Desktop Manager starts.

<table><thead><tr><th width="221">OPTION</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td>Use default workspace</td><td>Select the workspace to connect to when the application starts.</td></tr><tr><td>Last used workspace</td><td>Connect to the last used workspace.</td></tr><tr><td>Prompt for workspace</td><td>Prompt the user to for a workspace to connect to.</td></tr></tbody></table>

### System settings

Devolutions [workspaces](/rdm/getting-started/workspaces/workspace-types/native-workspaces.md) can manage a lot more settings related to the database and security. Those settings are saved directly in the database. For more information, please consult [System settings](/rdm/ribbon-menu-bar/administration/system-settings.md).
{% endtab %}

{% tab title="macOS" %}
Workspaces are at the heart of Remote Desktop Manager, acting as containers for entries.

### Settings

A workspace can be a local file or a database (either local or shared). Multiple workspaces can be managed at the same time as seen below.

### Create a workspace

Please consult [Create a workspace](/rdm/getting-started/workspaces/create-a-workspace.md) for more information.

### Multiple workspaces

Multiple workspaces can be configured, but there can only be one workspace active at a time. Switch from one workspace to another by using the workspace drop-down list.

### Startup workspace

You may assign a workspace to open automatically when Remote Desktop Manager starts.

<table><thead><tr><th width="212">OPTION</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td>Use default workspace</td><td>Select the workspace to connect to when the application starts.</td></tr><tr><td>Last used workspace</td><td>Connect to the last used workspace.</td></tr><tr><td>Prompt for workspace</td><td>Prompt the user to for a workspace to connect to.</td></tr></tbody></table>

### System settings

Devolutions [workspaces](/rdm/getting-started/workspaces/workspace-types/native-workspaces.md) can manage a lot more settings related to the database and security. Those settings are saved directly in the database. For more information, please consult [System settings](/rdm/ribbon-menu-bar/administration/system-settings.md).
{% endtab %}
{% endtabs %}

#### See also

* [Devolutions Academy - Choosing the right workspace](https://academy.devolutions.net/student/path/1916054/activity/2667043)


---

# 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.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.