> 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/pam/da/knowledge-base.md).

# Vidensbase

Udforsk vidensbasen for Devolutions PAM med vejledninger, tekniske referenceartikler og fejlfindingshjælp til administration af privilegeret adgang.

Vidensbasen for Devolutions PAM samler det praktiske materiale, De får brug for, når Deres opsætning af administration af privilegeret adgang kører: trinvise vejledninger, referenceartikler om PAM's mere tekniske muligheder og løsninger på problemer, De kan støde på.

* [Vejledningsartikler](/pam/da/knowledge-base/how-to-articles.md) fører Dem gennem konfiguration og udrulning af PAM-udbyder, fra Active Directory og Entra ID til brugerdefinerede domænekonti, sammen med daglige opgaver som rotation af adgangskoder og ophøjelse af privilegeret adgang.
* [Vidensbaseartikler](/pam/da/knowledge-base/knowledge-base-articles.md) dækker mere tekniske integrationer og referencemateriale, f.eks. automatisering med Ansible og Terraform, handlingsscripts til brugerdefinerede udbydere og partnerintegrationer.
* [Fejlfindingsartikler](/pam/da/knowledge-base/troubleshooting-articles.md) hjælper Dem med at løse problemer, der opstår med brugerdefinerede PAM-udbydere og deres handlingsscripts.


---

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