> 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/launcher/configuration-and-settings/devolutions-launcher-and-devolutions-server-synchronization.md).

# Devolutions Launcher and Devolutions Server synchronization

Set Devolutions Launcher as the default way to launch remote connections in Devolutions Server, either for all users or per account preferences.

Devolutions Launcher and Devolutions Server must be configured together to work. Launch connections can be set for all users in ***Devolutions Server Server Settings*** or individually in ***Account preferences***.

{% hint style="info" %}
You need to at least log in once to Devolutions Launcher for the companion tool to launch your sessions from Devolutions Server.
{% endhint %}

#### Server Settings

This method sets how all users launch remote connections.

In ***Administration - Server Settings - Advanced***, select ***Devolutions Launcher*** in the ***Launch connection with*** drop-down menu.

#### Account Preferences

This method sets how individual users open remote connections.

1. Click the ***User avatar***.
2. Select ***Preferences***.
3. Choose ***Devolutions Launcher*** from the ***Launch connection with*** drop-down menu and click ***Save***.


---

# 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/launcher/configuration-and-settings/devolutions-launcher-and-devolutions-server-synchronization.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.