> 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/remove-dsroleassignment.md).

# Remove-DSRoleAssignment

Remove-DSRoleAssignment quita una asignación de rol administrativo de principales o de un ámbito completo en una instancia de Devolutions Server.

### Sinopsis

Quitar una asignación de rol administrativo.

### Sintaxis

#### ByAssignee

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

#### WholeScope

```
Remove-DSRoleAssignment -RoleID <guid> -WholeScope -ScopeType <AdministrativeRoleAssignmentScopeType>
 [-ScopeID <guid[]>] [-WhatIf] [-Confirm] [<CommonParameters>]
```

### Descripción

Quitar principales concretos de un rol en uno o varios ámbitos, o usar -WholeScope para quitar en una sola llamada cada miembro del rol en esos ámbitos.

### Ejemplos

#### Ejemplo 1

```powershell
PS C:\> Remove-DSRoleAssignment -RoleID $role.Id -PrincipalId $userID -ScopeType Repository -ScopeID $vaultID
```

Quitar la asignación 'Propietario de la bóveda' de un solo usuario en una bóveda concreta.

#### Ejemplo 2

```powershell
PS C:\> Remove-DSRoleAssignment -RoleID $role.Id -ScopeType Repository -ScopeID $vaultID -WholeScope
```

Quitar cada principal que posee el rol en la bóveda. Solicita confirmación; pase -Confirm:$false para omitirla.

### 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 quitar el rol.

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

#### -RoleID

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

#### -ScopeID

ID de los recursos de ámbito de los que quitar las asignaciones: 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 las asignaciones que quitar. Obligatorio, no hay valor predeterminado, para evitar quitar 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: ''
```

#### -WholeScope

Quitar cada principal que posee el rol en los ámbitos indicados, en lugar de solo los principales enumerados en -PrincipalId.

```yaml
Type: System.Management.Automation.SwitchParameter
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: WholeScope
  Position: Named
  IsRequired: true
  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 Remove-DSRoleAssignment -detailed". Para obtener información técnica, escriba "Get-Help Remove-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/remove-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.