> 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/getting-started/create-and-run-an-account-discovery-configuration.md).

# Create and run an account discovery configuration

Create and run an account discovery configuration in Devolutions Server to scan a PAM provider and review the discovered accounts found.

An account discovery configuration is a set of instructions that dictate which provider to use, along with an optional recurrence schedule for periodically running the account discovery action on that provider.

1. To manage all existing account discovery configurations and create new ones, navigate to ***Administration – Privileged access – Account discovery configurations***. To create a new account discovery configuration, click on the ***Add a new account discovery configuration*** button.
2. Account discovery configurations can be applied to both managed and custom PAM providers. Either option can be chosen here.
3. Select a provider, choose ***Name*** for it, then click ***OK***.

{% hint style="success" %}
While any name can be assigned to a account discovery configuration, it is recommended to name it based on the provider it is associated with.
{% endhint %}

Upon creating the account discovery configuration, a job will be queued, indicated by an hourglass icon next to it. The job is scheduled by the Devolutions Server Windows service on the Devolutions Server host. Depending on the backlog, this process may take a few minutes.

Once the job is complete, the status will display a green check mark, and the results will be shown.

Each result represents an account that the account discovery action has found. If results are visible at this stage and they align with what the account discovery action returned, it indicates that the account discovery action is functioning correctly.

By clicking on the results, you can view all of the accounts identified by the account discovery action.

{% hint style="info" %}
For more information, refer to [Account discovery configurations](/pam/pam-with-devolutions-server/account-discovery-configurations.md).
{% endhint %}

### See also

* [Import accounts from an account discovery configuration](/pam/pam-with-devolutions-server/getting-started/import-accounts-from-an-account-discovery-configuration.md)
* [Import computers from Domain user providers in Devolutions Server](/pam/knowledge-base/how-to-articles/import-computers-from-domain-user-providers-in-devolutions-server.md)


---

# 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/getting-started/create-and-run-an-account-discovery-configuration.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.