> 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/import-accounts-from-an-account-discovery-configuration.md).
# Import accounts from an account discovery configuration
Once a list of accounts has been discovered, the next step is to import privileged accounts into a Devolutions PAM vault. If a vault was selected during the creation of the provider, a vault with the same name as the provider will have been created; otherwise, it will be necessary to [create one manually](https://docs.devolutions.net/pam/pam-with-devolutions-cloud/pam-vaults/#pam-vault-setup).
### Import accounts
1. To import accounts into a vault, select each discovered user and click on ***Import selected accounts***.
2. Select the ***Provider*** and the ***Path*** to the vault where the accounts will be added.
3. To reset passwords immediately for all imported accounts, select the ***Reset password on import*** option. This will automatically initiate a heartbeat and password rotation action on every imported account.
4. Click ***OK*** to import the accounts into the vault.
Once imported, the accounts should appear under the provider’s vault.
### Verifying heartbeat and password rotation actions on import
At this stage, the provider should have executed the heartbeat and password rotation actions, checking and resetting the account passwords if the ***Reset password on import*** option was selected. Verification of this process is recommended.
To verify, click on the account and navigate to the ***Logs*** category.
Within the logs, three key messages should be present:
* ***Entry added***: Indicates that a new account has been added to the vault.
* ***PAM password reset - Success***: Confirms that the provider executed the password rotation action and successfully changed the password. ***Check synchronization - Success***: Confirms that the heartbeat action compared the current password stored by Devolutions PAM with the password assigned to the account, confirming they match.
If all these messages are present, it can be confirmed that the provider has successfully executed all actions.
Although importing a new account into a vault automatically initiates a heartbeat and password rotation action, these actions can also be tested at any time.
While viewing the account in the vault, the heartbeat action can be tested by right-clicking on the account and selecting ***Check synchronization status:***
Or by clicking on the atom symbol:
If successful, the ***Check synchronization - Success*** message will appear in the account logs.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.devolutions.net/pam/pam-with-devolutions-server/getting-started/import-accounts-from-an-account-discovery-configuration.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
