> 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/de/powershell-commands/new-dcvaultpermission.md).

# New-DCVaultPermission

New-DCVaultPermission gewährt einem Benutzer oder einer Gruppe eine Tresorberechtigung in Devolutions Cloud, die über eine Rolle oder eine benutzerdefinierte Berechtigungsebene zugewiesen wird.

### Syntax

#### UserWithRolePermissions

```
New-DCVaultPermission -VaultId <guid> -UserId <guid> -VaultRoleId <guid> [-HubContext <HubContext>]
 [<CommonParameters>]
```

#### UserWithCustomPermissions

```
New-DCVaultPermission -VaultId <guid> -UserId <guid> -VaultPermission <VaultPermissionRole>
 [-HubContext <HubContext>] [<CommonParameters>]
```

#### GroupWithRolePermissions

```
New-DCVaultPermission -VaultId <guid> -GroupId <guid> -VaultRoleId <guid>
 [-HubContext <HubContext>] [<CommonParameters>]
```

#### GroupWithCustomPermissions

```
New-DCVaultPermission -VaultId <guid> -GroupId <guid> -VaultPermission <VaultPermissionRole>
 [-HubContext <HubContext>] [<CommonParameters>]
```

### Parameter

#### -GroupId

ID der Devolutions Cloud Group

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

Devolutions Cloud-Kontext

```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 des Devolutions Cloud User

```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 des Devolutions Cloud Vault

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

#### -VaultPermission

Benutzerdefinierte Tresorberechtigung festlegen

```yaml
Type: Devolutions.Hub.Clients.VaultPermissionRole
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: ''
```

#### -VaultRoleId

Vordefinierte Berechtigungen basierend auf Devolutions Cloud Vault Roles festlegen

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

#### CommonParameters

Dieses Cmdlet unterstützt die allgemeinen Parameter: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction und -WarningVariable. Weitere Informationen finden Sie unter [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Hinweise

Weitere Informationen erhalten Sie mit "Get-Help New-DCVaultPermission -detailed". Technische Informationen erhalten Sie mit "Get-Help New-DCVaultPermission -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/de/powershell-commands/new-dcvaultpermission.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.