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

# Problèmes d'espace de travail CyberArk

Résolvez les problèmes de l'espace de travail CyberArk dans Remote Desktop Manager, y compris les erreurs d'absence de licence et les échecs de permission de modification de compte.

Voici la liste de tous les problèmes connus de l'espace de travail CyberArk.

### Aucune licence trouvée

#### Solution

Pour effectuer les étapes de la [configuration initiale](/rdm/fr/getting-started/workspaces/workspace-types/alternative-workspaces/cyberark.md#first-connection), assurez-vous de vous connecter d'abord à un utilisateur qui possède les permissions CyberArk requises.

### Impossible de modifier un compte

#### Solution

L'espace de travail CyberArk reconnaîtra ***Add Safe*** comme l'administrateur. Cela contrôle également les actions d'ajout, de modification et de suppression dans l'interface utilisateur. Indépendamment de ***Add Safe***, CyberArk validera les permissions utilisateur appropriées lorsqu'une action est demandée (ajout/modification/suppression) et vous empêchera d'effectuer des tâches que l'utilisateur actuel n'est pas autorisé à effectuer.


---

# 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/fr/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.