> 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/powershell-commands/add-rdmroleassignment.md).

# Add-RDMRoleAssignment

Add-RDMRoleAssignment grants an administrative role to one or more users, user groups, or application identities at one or more scopes in Remote Desktop Manager.

### Synopsis

Assign an administrative role to users, user groups, or application identities.

### Syntax

#### \_\_AllParameterSets

```
Add-RDMRoleAssignment [-Role] <PSAdministrativeRole> [-User <PSUserInfo[]>] [-UserGroup <PSRoleInfo[]>]
 [-ApplicationIdentity <PSApplicationIdentityInfo[]>] -ScopeType <AdministrativeRoleAssignmentScopeType>
 [-ScopeID <guid[]>] [-ForcePromptAnswer <DialogResult[]>] [-WhatIf] [-Confirm] [<CommonParameters>]
```

### Description

Grant an administrative role to users, user groups, or application identities, at one or more scopes. Unlike Add-RDMUserVaultAccess, which always grants the workspace's configured vault-assignment role on a vault, this assigns any role at any scope the role supports.

### Examples

#### Example 1

```powershell
PS C:\> $role = Get-RDMAdministrativeRole -Name "Vault Owner"
PS C:\> $vault = Get-RDMVault -Name "Production"
PS C:\> Add-RDMRoleAssignment -Role $role -User (Get-RDMUser -Name "jsmith") -ScopeType Repository -ScopeID $vault.ID
```

Grants the 'Vault Owner' role to a user on a specific vault.

#### Example 2

```powershell
PS C:\> Add-RDMRoleAssignment -Role $role -ApplicationIdentity (Get-RDMApplicationIdentity -Name "MyServiceApp") -ScopeType Global
```

Grants a role to an application identity across the whole workspace.

#### Example 3

```powershell
PS C:\> Get-RDMAdministrativeRole -ScopeType Repository | Add-RDMRoleAssignment -UserGroup $groups -ScopeType Repository -ScopeID $vault1.ID, $vault2.ID
```

Grants every vault-assignable role to several user groups on two vaults.

### Parameters

#### -ApplicationIdentity

Application identities receiving the role

```yaml
Type: RemoteDesktopManager.PowerShellModule.PSOutputObject.PSApplicationIdentityInfo[]
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -Confirm

Prompts for confirmation before running the cmdlet.

```yaml
Type: System.Management.Automation.SwitchParameter
DefaultValue: False
SupportsWildcards: false
Aliases:
- cf
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -ForcePromptAnswer

Switch to use with caution. It will automatically answer prompt asking yes/no, yes/no/cancel, or ok/cancel questions. In case of multiple prompts, multiple values can be passed to this parameter. Here are the accepted values:

* Yes: Accept the prompt. Cover the OK and Automatic value.
* No: Refuse the yes/no/cancel prompt. "Cancel" is the fallback option if there is no "No" option.
* Cancel: Cancel the yes/no/cancel prompt. "No" is the fallback option if there is no "Cancel" option.

```yaml
Type: System.Windows.Forms.DialogResult[]
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -Role

Administrative role to assign

```yaml
Type: RemoteDesktopManager.PowerShellModule.PSOutputObject.PSAdministrativeRole
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: 0
  IsRequired: true
  ValueFromPipeline: true
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -ScopeID

IDs of the scope resources the role is assigned on: vault IDs when -ScopeType is Repository, gateway IDs when Gateway, PAM provider IDs when PamProvider, or business unit IDs when OrganizationalUnit. Required unless -ScopeType is Global

```yaml
Type: System.Guid[]
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -ScopeType

Scope type of the assignment. There is no default, so that a role is never silently assigned at the wrong scope

```yaml
Type: Devolutions.RemoteDesktopManager.AdministrativeRoleAssignmentScopeType
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: true
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -User

Users receiving the role

```yaml
Type: RemoteDesktopManager.PowerShellModule.PSOutputObject.PSUserInfo[]
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -UserGroup

User groups receiving the role

```yaml
Type: RemoteDesktopManager.PowerShellModule.PSOutputObject.PSRoleInfo[]
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -WhatIf

Shows what would happen if the cmdlet were to run. The cmdlet does not run.

```yaml
Type: System.Management.Automation.SwitchParameter
DefaultValue: False
SupportsWildcards: false
Aliases:
- wi
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Inputs

#### RemoteDesktopManager.PowerShellModule.PSOutputObject.PSAdministrativeRole

Administrative role to assign

### Notes

For more information, type "Get-Help Add-RDMRoleAssignment -detailed". For technical information, type "Get-Help Add-RDMRoleAssignment -full".


---

# 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/powershell-commands/add-rdmroleassignment.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.