> 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/es/powershell-commands/add-dsroleassignment.md).

# Add-DSRoleAssignment

Add-DSRoleAssignment concede un rol administrativo a uno o varios usuarios, grupos de usuarios o identidades de aplicación en uno o varios recursos de ámbito de Devolutions Server.

### Sinopsis

Asignar un rol administrativo a uno o varios principales en uno o varios ámbitos.

### Sintaxis

#### \_\_AllParameterSets

```
Add-DSRoleAssignment -RoleID <guid> -PrincipalId <guid[]> -ScopeType <AdministrativeRoleAssignmentScopeType>
 [-ScopeID <guid[]>] [-WhatIf] [-Confirm] [<CommonParameters>]
```

### Descripción

Conceder un rol a uno o varios usuarios, grupos de usuarios o identidades de aplicación en uno o varios recursos de ámbito. A diferencia de los cmdlets heredados Set-DSVaultUser/-UserGroup/-Application, esto establece el ID de recurso de ámbito que el servidor exige para que la asignación surta efecto.

### Ejemplos

#### Ejemplo 1

```powershell
PS C:\> $role = Get-DSAdministrativeRole | Where-Object Name -EQ 'Vault Owner'
PS C:\> Add-DSRoleAssignment -RoleID $role.Id -PrincipalId $userID -ScopeType Repository -ScopeID $vaultID
```

Conceder el rol 'Propietario de la bóveda' a un usuario en una bóveda concreta.

#### Ejemplo 2

```powershell
PS C:\> Add-DSRoleAssignment -RoleID $role.Id -PrincipalId $userID1, $userID2 -ScopeType Repository -ScopeID $vaultID1, $vaultID2
```

Conceder el rol a dos usuarios en dos bóvedas en una sola llamada (4 asignaciones en total).

### Parámetros

#### -Confirm

Solicita confirmación antes de ejecutar el cmdlet.

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

#### -PrincipalId

ID de los usuarios, grupos de usuarios o identidades de aplicación a los que asignar el rol.

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

#### -RoleID

ID del rol que asignar.

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

#### -ScopeID

ID de los recursos de ámbito en los que se asigna el rol: ID de bóveda cuando -ScopeType es Repository, ID de gateway cuando es Gateway, ID de proveedor de PAM cuando es PamProvider o ID de unidad de negocio cuando es OrganizationalUnit. Obligatorio salvo que -ScopeType sea Global; se ignora (con una advertencia) cuando -ScopeType es Global.

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

#### -ScopeType

Tipo de ámbito de la asignación. Obligatorio, no hay valor predeterminado, para evitar asignar en silencio en el ámbito incorrecto.

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

#### -WhatIf

Muestra lo que ocurriría si se ejecutara el cmdlet. El cmdlet no se ejecuta.

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

#### CommonParameters

Este cmdlet admite los parámetros comunes: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction y -WarningVariable. Para más información, consulte [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Notas

Para más información, escriba "Get-Help Add-DSRoleAssignment -detailed". Para obtener información técnica, escriba "Get-Help Add-DSRoleAssignment -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/es/powershell-commands/add-dsroleassignment.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.