> 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-dsprincipalroleassignment.md).

# Get-DSPrincipalRoleAssignment

Get-DSPrincipalRoleAssignment retrieves every administrative role assignment held by a user, user group, or application identity on a Devolutions Server instance.

### Synopsis

Get the administrative roles held by a user, user group, or application identity.

### Syntax

#### \_\_AllParameterSets

```
Get-DSPrincipalRoleAssignment -PrincipalId <guid> [-IncludeIndirect] [<CommonParameters>]
```

### Description

Get every administrative role assignment held by the given assignee, across every scope. Reverse lookup of Get-DSRoleAssignment: instead of "who holds a role at this scope", this answers "what roles does this assignee hold, anywhere". Use -IncludeIndirect to also surface roles granted to a user group the assignee belongs to; when an assignment came from a group, GroupID/GroupName identify that group and the assignment is not held directly by the assignee.

### Examples

#### Example 1

```powershell
PS C:\> Get-DSPrincipalRoleAssignment -PrincipalId $userID
```

Get every role directly assigned to the user.

#### Example 2

```powershell
PS C:\> Get-DSPrincipalRoleAssignment -PrincipalId $userID -IncludeIndirect
```

Also include roles the user holds through user group membership.

### Parameters

#### -IncludeIndirect

Also include roles granted to a user group the assignee belongs to, not just direct assignments.

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

#### -PrincipalId

ID of the user, user group, or application identity to look up.

```yaml
Type: System.Guid
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: true
  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.PSPrincipalRoleAssignment

### Notes

For more information, type "Get-Help Get-DSPrincipalRoleAssignment -detailed". For technical information, type "Get-Help Get-DSPrincipalRoleAssignment -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-dsprincipalroleassignment.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.