> 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/get-rdmadministrativerole.md).

# Get-RDMAdministrativeRole

Get-RDMAdministrativeRole retrieves the administrative roles that can be assigned in the current Remote Desktop Manager workspace.

### Synopsis

Retrieve the administrative roles available in the current workspace.

### Syntax

#### ID

```
Get-RDMAdministrativeRole [-ID] <guid> [-ScopeType <AdministrativeRoleAssignmentScopeType>]
 [-ForcePromptAnswer <DialogResult[]>] [<CommonParameters>]
```

#### Name

```
Get-RDMAdministrativeRole [[-Name] <string>] [-ScopeType <AdministrativeRoleAssignmentScopeType>]
 [-CaseSensitive] [-ForcePromptAnswer <DialogResult[]>] [<CommonParameters>]
```

### Description

Retrieve the administrative roles that can be assigned in the current workspace, optionally filtered by name, ID, or supported scope type. The cmdlet works with workspaces that manage access through administrative role assignments (currently only Devolutions Server).

### Examples

#### Example 1

```powershell
PS C:\> Get-RDMAdministrativeRole
```

Retrieves every administrative role available in the workspace.

#### Example 2

```powershell
PS C:\> Get-RDMAdministrativeRole -ScopeType Repository
```

Retrieves only the roles that can be assigned on a vault.

#### Example 3

```powershell
PS C:\> $role = Get-RDMAdministrativeRole -Name "Vault Owner"
PS C:\> $user = Get-RDMUser -Name "jsmith"
PS C:\> $user | Add-RDMRoleAssignment -RoleID $role.Id -ScopeType Repository -ScopeID $vault.ID
```

Resolves a role by name and assigns it to a user on a vault.

### Parameters

#### -CaseSensitive

Use case-sensitive name matching

```yaml
Type: System.Management.Automation.SwitchParameter
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: Name
  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: ''
```

#### -ID

Administrative role ID to retrieve

```yaml
Type: System.Guid
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: ID
  Position: 0
  IsRequired: true
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -Name

Filter by role name (supports wildcards)

```yaml
Type: System.String
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: Name
  Position: 0
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -ScopeType

Return only the roles that can be assigned at this scope type

```yaml
Type: System.Nullable`1[Devolutions.RemoteDesktopManager.AdministrativeRoleAssignmentScopeType]
DefaultValue: ''
SupportsWildcards: false
Aliases: []
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).

### Outputs

#### RemoteDesktopManager.PowerShellModule.PSOutputObject.PSAdministrativeRole

### Notes

For more information, type "Get-Help Get-RDMAdministrativeRole -detailed". For technical information, type "Get-Help Get-RDMAdministrativeRole -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/get-rdmadministrativerole.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.