For the complete documentation index, see llms.txt. This page is also available as Markdown.

Get started with Devolutions Cloud

Once your Devolutions Cloud workspace is created, the next step is to set it up for your team. This article walks you through activating and assigning your licenses, inviting a second administrator, and creating the user groups and vaults that organize access across your organization.

Activate your license and assign it

  1. Open your Devolutions Cloud.

  2. Go to AdministrationLicenses.

  3. Enter your license information (for example, a starter pack or another license type).

  4. Assign a license to the appropriate user.

  5. Optionally, enable the option to automatically assign a license when onboarding new users, or auto-assign licenses to specific user groups.

Invite a second administrator

While not required, a second administrator adds redundancy in case the owner loses access and makes it easier to share the workload during setup.

  1. Go to AdministrationUsers.

  2. Select Invite users.

  3. Enter the email address of the person to invite and assign the Administrator role.

  4. Choose how the invited user will authenticate (see below).

  5. Optionally, allow the user to use Devolutions Cloud in offline mode for apps such as Workspace and Remote Desktop Manager.

  6. Send the invitation.

Devolutions Cloud supports three authentication methods, and the invitation flow differs slightly depending on which you use:

  • Devolutions account: If the invitee has no account, they receive a welcome email with a temporary password to create one. If they already have one, they receive a link to join the Devolutions Cloud directly.

  • Single sign-on (SSO): Integrates with Microsoft or Okta and supports account provisioning. Requires configuration beforehand.

  • Encryption service: A self-hosted option that delivers encryption keys to users so they can access your Devolutions Cloud with their key.

Create user groups

User groups streamline onboarding: new members can be auto-assigned to the right group, granted licenses, and given preset permissions from the start.

Administrators always have access to all areas of the system, so they do not need to be added to a user group.

  1. Go to AdministrationManagementUser groups.

  2. Select Add.

  3. Name the group based on department, location, or job role.

  4. Add the relevant users.

  5. Assign the predefined roles and permissions for the group.

  6. Save the group.

Create and configure vaults

Every Devolutions Cloud includes two vaults by default: a default vault (a shared space you can rename and repurpose) and a user vault (a private vault for each member's personal work-related items, such as passwords, website logins, and alarm codes). User vaults can be disabled when inviting non-admin users.

  1. Create additional vaults by going to AdministrationVaults and choosing the appropriate vault type for the contents you want to store.

  2. Assign the appropriate user group permissions to each vault.

Rename the default vault

  1. Go to AdministrationVaults.

  2. Select the default vault.

  3. Select Edit.

  4. Rename it to suit your organization.

Set the vault visibility

When creating or editing a vault, choose its visibility:

  • Public: Users can see that the vault exists even without access to its contents, and can request access from the vault menu for an administrator to approve or deny.

  • Private: The vault is hidden unless a user is explicitly granted access or invited; users cannot request access.

Set the vault content type

Set the vault content type to restrict the kind of entries the vault may contain.

Assign permissions

  1. Go to AdministrationVaults.

  2. Select the default vault.

  3. Select Edit.

  4. Open the vault's Security tab.

  5. Assign permissions to individual users and user groups using the predefined roles.

  6. Select the eye icon to preview what a role includes, or select View role definitions to see the full permissions chart.

  7. Optionally, override a role with custom permissions for a more granular approach.

See also

Last updated

Was this helpful?