> 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/powershell/devolutions-cloud-powershell/powershell-module.md).

# PowerShell module

Install the Devolutions.PowerShell module and connect to Devolutions Cloud to create, retrieve, and update vaults and entries via PowerShell.

The [Devolutions.PowerShell module](/powershell/remote-desktop-manager-powershell/devolutions.powershell-core-module.md) is a way to access, create, update, and remove elements in Devolutions Cloud. This will help you to automate some operations/scripts. After you install the Devolutions.PowerShell module, you will be ready to use the module and connect to your Devolutions Cloud instance.

### Prerequisites

* PowerShell 7.4 or later installed:
  * [Windows](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows)
  * [macOS](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-macos)
  * [Linux](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-linux)
* An [application user](https://docs.devolutions.net/cloud/web-interface/administration/management/application-identities/manage-application-identities)

### Connecting to your Devolutions Cloud instance

{% hint style="info" %}
For the full list of available commands, see [PowerShell commands](/powershell/powershell-commands.md). Other installation options can be found in the [PowerShell Gallery](https://www.powershellgallery.com/packages/devolutions.powershell/).
{% endhint %}

{% hint style="info" %}
Starting with version 2026.2 of the Devolutions.PowerShell module, Devolutions Cloud commands use the `DC` prefix instead of `Hub` (for example, `Get-DCVault` instead of `Get-HubVault`). The former `Hub` command names remain available as aliases, so existing scripts keep working.
{% endhint %}

1. Once PowerShell 7.4 or later is installed, open a PowerShell terminal and install the Devolutions.PowerShell module with the following command: `Install-Module -Name Devolutions.Powershell`
2. Connect to Devolutions Cloud using the command below. If you do not see an error, it means you are connected to your Devolutions Cloud instance.

   `Connect-DCAccount -Url https<area>://yourhub.devolutions.app/ -ApplicationSecret [YOUR_APPLICATION_SECRET] -ApplicationKey [YOUR_APPLICATION_KEY]`

### Command example and use

1. With the `Get-DCVault` command, you can get vaults that your application user can view and edit. If you have set the permissions of your application user to multiple vaults, you will see an array of vaults.
2. With this vault information, you can get all of the entries with the command `Get-DCEntry` and the vault ID. If you have more than one entry, you will see an array of entries.
3. To view specific information, you can put the Devolutions Cloud command return to a variable and retrieve what you need, like the connection ID in this example:
4. To edit this entry, you can change the object and update it with the `Set-DCEntry` command.

At any moment, you can validate in your web version of Devolutions Cloud that the changes have been made.


---

# 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/powershell/devolutions-cloud-powershell/powershell-module.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.