> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/user-and-team-provisioning/ldap-provisioning.md).
# LDAP Provisioning
Keeper AD Bridge supports automatic provisioning of nodes, roles, teams and users from any LDAP service.
The Keeper Bridge is an enterprise-class service application that supports the ability to automatically sync Nodes, Users, Roles and Teams to your Keeper Enterprise account from an LDAP service. To activate and install the Keeper Bridge, follow the below steps:
1. Log in to the [Admin Console](https://keepersecurity.com/console).
2. Create a Node (under the root node) to sync with your LDAP directory.
3. Visit the **Provisioning** tab and select **Add Method** and then select **LDAP Sync**.
4. Download the Keeper Bridge and proceed with setup.
{% hint style="info" %}
For detailed Bridge setup and install instructions see our [Keeper Bridge Guide](https://docs.keeper.io/keeper-bridge).
{% endhint %}
* The Keeper Bridge does not authenticate users into their vault with their LDAP password. For seamless user authentication, consider our [Keeper SSO Connect](/enterprise-guide/user-and-team-provisioning/single-sign-on-saml-2.0-authentication.md) add-on as described in the next section which authenticates against Active Directory via AD FS.
* Automated Team provisioning requires the Keeper Administrator to authenticate on the Keeper Bridge. The Bridge will poll for users who have created their Keeper account after invitation, then the Bridge will encrypt the Team Key with the user's public key, and distribute the Team Key to the user. Once any member of the team logs into the Vault, all members of that team are approved.
* Once the Keeper Bridge is syncing, we recommend not making manual user or team changes directly on the Admin Console. Delegate all user and team provisioning to the bridge through the LDAP Directory. Role enforcement policy changes should still be made on the Admin Console.
---
# 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.keeper.io/enterprise-guide/user-and-team-provisioning/ldap-provisioning.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.