> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/partek/partek-flow/user-manual/settings/system/ldap-configuration.md).
# LDAP Configuration
Partek Flow user accounts can be tied to an organization’s Lightweight Directory Access Protocol (LDAP) database. These can be configured by administrator accounts using the LDAP Configuration menu (Figure 1). Click on the 
icon to edit the LDAP configuration. Enter the settings relevant to your domain. Consult with your organization’s LDAP database administrator for assistance with configurations. For more information about any of the fields, mouse over the 
.
Once the LDAP settings have been successfully configured, proceed to the User management section of the Settings page then click on 
. The Source field should denote the name of the LDAP configuration entered. Typing a few characters of the username will prompt Partek Flow to suggest users that are available in your LDAP database to add.
## Additional Assistance
If you need additional assistance, please visit [our support page](http://www.partek.com/support) to submit a help ticket or find phone numbers for regional support.
---
# 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://help.bioinsight.illumina.com/partek/partek-flow/user-manual/settings/system/ldap-configuration.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.