> 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/pam-with-devolutions-server/account-discovery-configurations.md).
# Account discovery configurations
Configure account discovery in Devolutions Server to scan providers for accounts, import them into PAM vaults, and manage JIT group assignments.
Account discovery configurations are the instances that discover accounts of a provider's environment. The types of account discovery configurations match the supported Devolutions Server providers.
To see the results of a scanning operation, click on the eye-shaped ***view result*** icon or the number shown in the ***Results*** column of a particular account discovery configuration.
To manage privileged accounts with the Devolutions Server PAM feature, select the accounts from the ***Account discovery configurations*** result page and click on the ***Import selected computers*** button. The accounts should then be available in the ***Privileged access*** section.
#### Import
| Option | Description |
| ---------------------------- | ------------------------------------------------------------------------------------------- |
| **Provider** | Select the [provider](/pam/pam-with-devolutions-server/providers.md) in the drop-down list. |
| **Path** | Select the destination path for the imported accounts. |
| **Account lifecycle policy** | Select the lifecycle policy source to apply to the imported accounts. |
| **Reset password on import** | Resets the password when the account is imported. |
#### Manage group assignments from scan results
From the scan results of an account discovery configuration, PAM operators can view the group assignments of a discovered account and manage them directly.
To open the group assignment form, select a discovered account in the scan results. The form displays the account details and a list of its assigned groups, each with an associated risk score and a checkbox for selection.
#### Add groups to JIT elevation
1. In the scan results, select a discovered account.
2. In the group assignment form, select one or more groups using the checkboxes.
3. Click ***Add to JIT***.
4. A confirmation message appears listing each group with a status of **Added** or **Duplicate**.
#### Remove group memberships
1. In the scan results, select a discovered account.
2. In the group assignment form, select one or more groups using the checkboxes.
3. Click ***Remove assignment***.
4. In the confirmation prompt, click ***Remove*** to confirm.
5. A confirmation message lists all groups the account was successfully removed from.
The ***Remove assignment*** button is only enabled when at least one group is selected.
### See also
* [Devolutions Academy – Discovering your credentials using scans](https://academy.devolutions.net/student/path/2354099/activity/4305212)
---
# 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/pam-with-devolutions-server/account-discovery-configurations.md?ask=&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.