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

# Get-DSEntityResolvedPermissions

Get-DSEntityResolvedPermissions returns the resolved permissions of a Devolutions Server entry, folder, PAM entry, or PAM folder.

### Synopsis

Get the resolved permissions of an entity

### Syntax

#### \_\_AllParameterSets

```
Get-DSEntityResolvedPermissions [-ID] <guid> [-ResolveNameToID] [<CommonParameters>]
```

### Description

Get the resolved permissions of an entity. It can be an entry, a folder, a PAM entry, or PAM folder. Administrators always have all the rights even if they are not specified. A warning will be given if an application has the same name as a user or another application. It that case, it is possible the returned ID is the wrong one. To use the cmdlet, you must be an administrator.

### Examples

```powershell
PS C:\> $resolvedPermissions = Get-DSEntityResolvedPermissions -ID $entityID
PS C:\> $resolvedPermissions |
          Where { $_.Override -eq [Devolutions.RemoteDesktopManager.SecurityRoleOverride]::Everyone -or $_.Roles -Contains $userID} |
          Select -ExpandProperty Right
```

Find all the rights the user identified by $userID have on the entity identified by $entityID.

### Parameters

#### -ID

Entity whose permissions will be resolved. It can be an entry, a folder, a PAM account, or a PAM folder.

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

#### -ResolveNameToID

Convert to names to their IDs.

```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: ''
```

#### 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).

### Notes

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