> 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/checklist-for-third-party-team-workspaces.md).
# Checklist for Third-Party Team workspaces
{% tabs %}
{% tab title="Windows" %}
Here is a checklist designed to help IT administrators install and configure Remote Desktop Manager for their team with a third-party workspace.
[Download](https://devolutions.net/remote-desktop-manager/download/) and install Remote Desktop Manager before proceeding.
| Checklist for third-party team workspaces | Description |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Step 1 - [Configure and create the SQL workspace](https://www.youtube.com/watch?v=BfFvtHJSzbs\&t=81s) | Upon first launch, Remote Desktop Manager prompts you to select a workspace. Devolutions integrates the following Third-party Team workspaces:
You need to enter general workspace information such as the name and the host.
For the first database user, create an SQL administrator account with the Database login mode. Then, create the database and set up initial parameters for the default vault
|
| [Overview of authentication and login types](https://www.youtube.com/watch?v=BfFvtHJSzbs\&t=174s) | Users will authenticate using the method of your choosing:
- Database login: Uses an SQL login to directly access the SQL server. The first database administrative user is created using this method.
- Integrated Security (Active Directory): Recommended for Azure SQL workspaces. Uses the active user’s Microsoft AD account.
- Custom login: Recommended for SQL Server workspaces. Allows for the creation of Remote Desktop Manager accounts for users to authenticate with, but prevents them from having direct access to the SQL database through an external tool.
|
| Step 2 - Register your license
| It is to possible to obtain 14-day trials for the Devolutions ecosystem or a full version of Remote Desktop Manager.
You can enable the option to have licenses auto-assigned, so that when new users are created they automatically receive a license.
Assign a license to the administrator account previously created so that you can create more administrative accounts. This license can be freed up later on.
|
| Step 3 - [Create the "custom login" Remote Desktop Manager and SQL account](https://www.youtube.com/watch?v=BfFvtHJSzbs\&t=359s) | Create a new administrative SQL user with just enough read/write permissions on the SQL side to accomplish what they need to do in Remote Desktop Manager without having complete control over the SQL server itself. Use the ***Database Authentication type*** for this account so it can create both a Remote Desktop Manager login and an SQL account login. |
| Step 4 - [Create the administrator user account](https://www.youtube.com/watch?v=BfFvtHJSzbs\&t=412s) | Create the account that the administrator will use daily to access Remote Desktop Manager. Use the Custom (Devolutions) Authentication type for this account.
Once this daily account is created, you can update the workspace with the correct login information to reflect that this new administrative account is used instead of the first account.
It is now safe to delete the first database account and to unassign the license of the administrative SQL user.
|
| Step 5 - [Create remaining user accounts](https://www.youtube.com/watch?v=BfFvtHJSzbs\&t=514s) | Add all other users one by one using the ***Authentication type*** of your choice. See the [Overview of Authentication and Login Types](https://youtu.be/BfFvtHJSzbs\&t=174s) or [User Management](https://docs.devolutions.net/rdm/commands/administration/user-management/) for more information. |
| Step 6 - [Create user groups](https://www.youtube.com/watch?v=BfFvtHJSzbs\&t=552s) | Create user groups and assign previously created users to those groups. Each user can be part of predefined permissions in user groups, which helps you manage who has access to which resources and what they can do with them without having to individually manage them. |
| Step 7 - [Create vaults](https://www.youtube.com/watch?v=BfFvtHJSzbs\&t=602s) | In Remote Desktop Manager, data is stored in a hierarchy of folders and entries all within vaults. The number of vaults created and the way they are categorized is completely up to you, but we have seen great success in teams separating their content by departments, locations, and customer accounts.
All users have access to the default vault created after installing Remote Desktop Manager. You can change its configuration as well as create other vaults, then assign them users and user groups.
Access all vaults using the vault selector in the navigation pane. Each user can also access their own user vault. This vault is only accessible to them and is a great place to store business-related entries for the user, such as alarm codes, user credentials, websites, documents, etc.
|
| Step 8 - [Assign permissions](https://www.youtube.com/watch?v=BfFvtHJSzbs\&t=700s) | Permissions can be granted to users and user groups. They are set on the vault, folder, and entry levels.
The permissions granted on the folder can be inherited by each entry set under that folder.
It is possible to batch grant access permissions and permission sets to users and user groups.
|
| Step 9 - [Add a security provider for encryption](https://www.youtube.com/watch?v=BfFvtHJSzbs\&t=933s) | Remote Desktop Manager encrypts all passwords and sensitive information with AES-256 encryption, but some organizations may require for the whole database to be encrypted.
The Security Provider is an additional level of encryption to the already-encrypted passwords and sensitive information. It can be configured using a passphrase, a certificate, or a keyfile. See our Security providers best practices.
|
| Step 10 - [Deploy to workstations](https://www.youtube.com/watch?v=BfFvtHJSzbs\&t=1072s) | Deploy Remote Desktop Manager to your end users using the custom installer service, which creates a customized MSI package that can be installed or deployed. It contains a fully packaged version of Remote Desktop Manager along with all of the workspace information required for a user to access the database.
The MSI can then be manually installed or silently pushed to workstations using a deployment tool.
|
| {% endtab %} | |
{% tab title="macOS" %}
Here is a checklist designed to help IT administrators install and configure Remote Desktop Manager for their team with a third-party workspace.
[Download](https://devolutions.net/remote-desktop-manager/download/) and install Remote Desktop Manager before proceeding.
| Checklist for third-party team workspaces | Description |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Step 1 - Configure and create the SQL workspace | Upon first launch, Remote Desktop Manager prompts you to select a workspace. Devolutions integrates the following Third-party Team workspaces:
You need to enter general workspace information such as the name and the host.
For the first database user, create an SQL administrator account with the Database login mode. Then, create the database and set up initial parameters for the default vault.
|
| Overview of authentication and login types | Users will authenticate using the method of your choosing:
- Database login: Uses an SQL login to directly access the SQL server. The first database administrative user is created using this method.
- Integrated Security (Active Directory): Recommended for Azure SQL workspaces. Uses the active user’s Microsoft AD account.
- Custom login: Recommended for SQL Server workspaces. Allows for the creation of Remote Desktop Manager accounts for users to authenticate with, but prevents them from having direct access to the SQL database through an external tool.
|
| Step 2 - Register your license
| It is to possible to obtain 14-day trials for the Devolutions ecosystem or a full version of Remote Desktop Manager.
You can enable the option to have licenses auto-assigned, so that when new users are created they automatically receive a license.
Assign a license to the administrator account previously created so that you can create more administrative accounts. This license can be freed up later on.
|
| Step 3 - Create the "custom login" Remote Desktop Manager and SQL account | Create a new administrative SQL user with just enough read/write permissions on the SQL side to accomplish what they need to do in Remote Desktop Manager without having complete control over the SQL server itself. Use the ***Database Authentication type*** for this account so it can create both a Remote Desktop Manager login and an SQL account login. |
| Step 4 - Create the administrator user account | Create the account that the administrator will use daily to access Remote Desktop Manager. Use the Custom (Devolutions) Authentication type for this account.
Once this daily account is created, you can update the workspace with the correct login information to reflect that this new administrative account is used instead of the first account.
It is now safe to delete the first database account and to unassign the license of the administrative SQL user.
|
| Step 5 - Create remaining user accounts | Add all other users one by one using the ***Authentication type*** of your choice. See the [Overview of Authentication and Login Types](https://youtu.be/BfFvtHJSzbs\&t=174s) or [User Management](https://docs.devolutions.net/rdm/commands/administration/user-management/) for more information. |
| Step 6 - Create user groups | Create user groups and assign previously created users to those groups. Each user can be part of predefined permissions in user groups, which helps you manage who has access to which resources and what they can do with them without having to individually manage them. |
| Step 7 - Create vaults | In Remote Desktop Manager, data is stored in a hierarchy of folders and entries all within vaults. The number of vaults created and the way they are categorized is completely up to you, but we have seen great success in teams separating their content by departments, locations, and customer accounts.
All users have access to the default vault created after installing Remote Desktop Manager. You can change its configuration as well as create other vaults, then assign them users and user groups.
Access all vaults using the vault selector in the navigation pane. Each user can also access their own user vault. This vault is only accessible to them and is a great place to store business-related entries for the user, such as alarm codes, user credentials, websites, documents, etc.
|
| Step 8 - Assign permissions | Permissions can be granted to users and user groups. They are set on the vault, folder, and entry levels.
The permissions granted on the folder can be inherited by each entry set under that folder.
It is possible to batch grant access permissions and permission sets to users and user groups.
|
| Step 9 - Add a security provider for encryption | Remote Desktop Manager encrypts all passwords and sensitive information with AES-256 encryption, but some organizations may require for the whole database to be encrypted.
The Security Provider is an additional level of encryption to the already-encrypted passwords and sensitive information. It can be configured using a passphrase, a certificate, or a keyfile. See our Security providers best practices.
|
| Step 10 - Deploy to workstations | Deploy Remote Desktop Manager to your end users using the custom installer service, which creates a customized MSI package that can be installed or deployed. It contains a fully packaged version of Remote Desktop Manager along with all of the workspace information required for a user to access the database.
The MSI can then be manually installed or silently pushed to workstations using a deployment tool.
|
| {% endtab %} | |
| {% endtabs %} | |
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.devolutions.net/rdm/getting-started/checklist-for-third-party-team-workspaces.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.