> 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/rdm/es/knowledge-base/troubleshooting-articles/cyberark-workspace-issues.md).

# Problemas del espacio de trabajo de CyberArk

Resuelva los problemas del espacio de trabajo de CyberArk en Remote Desktop Manager, incluidos los errores de licencia no encontrada y los fallos de permisos de edición de cuentas.

Aquí tiene la lista de todos los problemas conocidos del espacio de trabajo de CyberArk.

### No se ha encontrado ninguna licencia

#### Solución

Para realizar los pasos de [configuración inicial](/rdm/es/getting-started/workspaces/workspace-types/alternative-workspaces/cyberark.md#first-connection), asegúrese de conectarse primero con un usuario que tenga los permisos de CyberArk necesarios.

### No se puede editar una cuenta

#### Solución

El espacio de trabajo de CyberArk reconocerá ***Add Safe*** como el administrador. Esto también controla las acciones de añadir/editar/eliminar en la interfaz de usuario. Independientemente de ***Add Safe***, CyberArk validará los permisos de usuario correctos cuando se solicite una acción (añadir/editar/eliminar) y le impedirá realizar tareas que el usuario actual no esté autorizado a realizar.


---

# 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/rdm/es/knowledge-base/troubleshooting-articles/cyberark-workspace-issues.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.