> 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/set-dsentitypermission.md).

# Set-DSEntityPermission

### Synopsis

Sets the permissions on a given entity.

### Syntax

#### \_\_AllParameterSets

```
Set-DSEntityPermission [-EntityId] <guid> [[-Permissions] <PSPermissionWrapper[]>]
 [[-PermissionOverride] <SecurityRoleOverride>] [-OverrideExistingPermissions] [-AsLegacyResponse]
 [<CommonParameters>]
```

### Description

Sets the permissions on a given entity (Vault, folder or entry).

### Examples

#### Example 1

$Permissions = @( \[Devolutions.RemoteDesktopManager.Business.ConnectionPermission]@{ Override = \[Devolutions.RemoteDesktopManager.SecurityRoleOverride]::Custom Right = \[Devolutions.RemoteDesktopManager.SecurityRoleRight]::View Roles = @($UserId1, $UserId2, $RoleId1) }, \[Devolutions.RemoteDesktopManager.Business.ConnectionPermission]@{ Override = \[Devolutions.RemoteDesktopManager.SecurityRoleOverride]::Inherited Right = \[Devolutions.RemoteDesktopManager.SecurityRoleRight]::Edit Roles = @($UserId1, $UserId2, $RoleId1) } ) > Set-DSEntityPermissions -EntityId $ID -Permissions $Permissions

* To override already existing permissions, please use the 'OverrideExistingPermissions' switch parameter. - When using this CMDlet, your entity's override mode will default to 'Custom'. Use the 'PermissionOverride' parameter if you wish to set it to anything else.

#### Example 2

```powershell
PS C:\> Set-DSEntityPermissions -EntityId $ID -PermissionOverride 'Default'
```

For the entry whose ID is stored in $ID, all its permissions will be inherited from the parent.

#### Example 3

```powershell
PS C:\> $userIDs = Get-DSUser | Where Name -like *something* | Select -ExpandProperty ID
        $permission = New-DSEntityPermission -Override CustomInherited -Right Edit -ID $userIDs
        Set-DSEntityPermission -EntityID $entryID -Permissions $permission
```

Add users whose name contains 'something' to the inherited users who canedit the entry whose ID is stored in $entryID

### Parameters

#### -AsLegacyResponse

In versions prior to 2024.2, many DS cmdlets returned a ServerResponse object. Enabling this backward compatibility switch allows scripts developed for earlier versions to function correctly.

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

#### -EntityId

ID of the entity for which you want to change the permissions

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

#### -OverrideExistingPermissions

Override existing permissions. Without this parameter, all exisiting custom permissions won't be overwritten by those specified with the parameter Permissions.

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

#### -PermissionOverride

Determines the permissions for the entry. If not specified and the parameter Permissions is used, it will be set to 'Custom'. Four options are available Default => Inherits the permissions from the parent groups. Custom => Lets you specify a custom value for each of the permission. Everyone => Same as Allowed in the UI. Grants all the permissions to everyone. Never => Same as Disallowed in the UI. Grants the permission to no one but the administrators.

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

#### -Permissions

Permission object. The object can be created from New-DSEntityPermission or directly from the type \[Devolutions.RemoteDesktopManager.Business.ConnectionPermission].

```yaml
Type: RemoteDesktopManager.PowerShellModule.PSOutputObject.PSWrapper.PSPermissionWrapper[]
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: 1
  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 Set-DSEntityPermission -detailed". For technical information, type "Get-Help Set-DSEntityPermission -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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.devolutions.net/powershell/powershell-commands/set-dsentitypermission.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.