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

# Problemer med CyberArk-arbejdsområde

Løs problemer med CyberArk-arbejdsområder i Remote Desktop Manager, herunder fejlen ingen licens fundet og fejl i tilladelsen til at redigere konti.

Her er listen over alle kendte problemer med CyberArk-arbejdsområder.

### Ingen licens fundet

#### Løsning

For at udføre trinnene i den [indledende konfiguration](/rdm/da/getting-started/workspaces/workspace-types/alternative-workspaces/cyberark.md#first-connection) skal De først oprette forbindelse med en bruger, der har de nødvendige CyberArk-tilladelser.

### Kan ikke redigere en konto

#### Løsning

CyberArk-arbejdsområdet genkender ***Add Safe*** som administratoren. Det styrer også handlingerne tilføj, rediger og slet i brugergrænsefladen. Uanset ***Add Safe*** validerer CyberArk de korrekte brugertilladelser, når en handling anmodes, og forhindrer Dem i at udføre opgaver, som den aktuelle bruger ikke har tilladelse til.


---

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