> 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/server/knowledge-base/how-to-articles/link-accounts-in-devolutions-server.md).

# Link accounts in Devolutions Server

Link accounts in Devolutions Server so a user can manage a regular and a privileged account together, switching between them at login.

The ***Linked account*** feature allows users to associate another account under the same user. This feature is particularly beneficial when a user needs to manage different accounts. For instance, a user may have an account with the email address "<bob@windjammer.co>" and another account with the email address "<_bob@windjammer.co>", which serves as an elevated or privileged account.

{% hint style="info" %}
Both users need to be created before linking them together.
{% endhint %}

The primary purpose of ***Linked account*** is to enhance user convenience and streamline account management.

1. Log in to Devolutions Server with an administrator account.
2. Go to ***Administration*** – ***Security Management*** – ***Users***.
3. Select one of the users you want to pair, then click on ***Edit***.
4. Go to the ***Linked account*** tab.
5. Select the other account from the dropdown.
6. Click ***Update*** to save the changes and close the window.

The accounts are now linked. The ***Linked account*** column shows which account is paired to one another.

{% hint style="info" %}
There is no primary or secondary account functionality with this feature; meaning the order in which they are linked does not matter and each can be unlinked to then be linked to a different account without issue.

To switch between both accounts, it is required to log out and log in with the second account.
{% endhint %}


---

# 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/server/knowledge-base/how-to-articles/link-accounts-in-devolutions-server.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.