> 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/fr/powershell-commands/set-dcentrypermission.md).

# Set-DCEntryPermission

Set-DCEntryPermission accorde à un utilisateur ou à un groupe des permissions basées sur les rôles ou personnalisées sur une entrée précise dans un coffre Devolutions Cloud.

### Syntaxe

#### UserWithRolePermissions

```
Set-DCEntryPermission -VaultId <guid> -EntryId <guid> -UserId <guid> -EntryRoleId <guid>
 [-HubContext <HubContext>] [<CommonParameters>]
```

#### UserWithCustomPermissions

```
Set-DCEntryPermission -VaultId <guid> -EntryId <guid> -UserId <guid>
 -EntryPermission <EntryPermissionRole> [-HubContext <HubContext>] [<CommonParameters>]
```

#### GroupWithRolePermissions

```
Set-DCEntryPermission -VaultId <guid> -EntryId <guid> -GroupId <guid> -EntryRoleId <guid>
 [-HubContext <HubContext>] [<CommonParameters>]
```

#### GroupWithCustomPermissions

```
Set-DCEntryPermission -VaultId <guid> -EntryId <guid> -GroupId <guid>
 -EntryPermission <EntryPermissionRole> [-HubContext <HubContext>] [<CommonParameters>]
```

### Paramètres

#### -EntryId

ID de l'entrée Devolutions Cloud

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

#### -EntryPermission

Définir une permission d'entrée personnalisée

```yaml
Type: Devolutions.Hub.Clients.EntryPermissionRole
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: UserWithCustomPermissions
  Position: Named
  IsRequired: true
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
- Name: GroupWithCustomPermissions
  Position: Named
  IsRequired: true
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -EntryRoleId

Définir des permissions prédéfinies en fonction des rôles d'entrée Devolutions Cloud

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

#### -GroupId

ID du groupe Devolutions Cloud

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

#### -HubContext

Contexte Devolutions Cloud

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

#### -UserId

ID de l'utilisateur Devolutions Cloud

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

#### -VaultId

ID du coffre Devolutions Cloud

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

Cette applet de commande prend en charge les paramètres communs : -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction et -WarningVariable. Pour plus d'informations, consultez [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Notes

Pour plus d'informations, tapez « Get-Help Set-DCEntryPermission -detailed ». Pour des informations techniques, tapez « Get-Help Set-DCEntryPermission -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/fr/powershell-commands/set-dcentrypermission.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.