> 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/providers/custom-pam-providers/windows-local-accounts.md).

# Windows local accounts

The Windows local accounts custom PAM provider manages local Windows accounts across multiple hosts, extending the single-host provider.

The ***Windows local accounts*** provider enables the management of local Windows accounts across multiple hosts. While the ***Windows account*** provider already exists within Devolutions Server, it is limited to managing accounts on a single host. This custom PAM provider extends that capability.

The pre-built template for this custom PAM provider can be found [on GitHub](https://github.com/Devolutions/PAM-Providers/tree/master/Providers/Windows%20Accounts).

### General

| Option        | Description                   |
| ------------- | ----------------------------- |
| Name          | Display name of the Provider. |
| Template name | Template of the Provider.     |

### Properties

| Option                             | Description                                                           |
| ---------------------------------- | --------------------------------------------------------------------- |
| Description                        | Description of the provider.                                          |
| Host                               | IP Address or host name where the Windows local accounts are located. |
| ExcludeDisabledAccountsInDiscovery | Exclude disabled accounts when in discovery mode.                     |
| HostsLDAPSearchFilter              | Add LDAP search filter(s).                                            |

### Credentials

| Option            | Description                                                         |
| ----------------- | ------------------------------------------------------------------- |
| Credential type   | Custom credentials or Linked credential options.                    |
| Username          | Username of the Windows local account with rights to list accounts. |
| Password          | Password of the Windows local account.                              |
| Linked credential | Credential directly linked to a PAM account.                        |

### Actions

| Option                                    | Description                                                      |
| ----------------------------------------- | ---------------------------------------------------------------- |
| Add PAM vault                             | Will create a PAM vault with the provider's name if enabled.     |
| Add a new account discovery configuration | Will open the Account discovery configuration dialog if enabled. |


---

# 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/providers/custom-pam-providers/windows-local-accounts.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.