> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/connector-configuration/2-configparam.md).
# Connector parameters
This section describes how to define the configuration parameters for a connector
Since each connector is different, OpenIAM allows you to define the parameters which should be configured for the parameter. This applies to both connectors provided by OpenIAM as well as connectors that are developed by partners and customers.
Each of the pre-registered connectors are already configured. The documentation for each connector also includes which parameters need to be configured. The screen below provides an example of the configuration parameters required for the SCIM connector. You will notice that it contains both a mix of standard configuration options and several custom parameters which are unique to the SCIM connector.
The fields are grouped — **Connection**, **Operation Handlers**, **Directory & Search**, **User Objects** and **Group Objects** — and the header counts how many of the 25 are configured, so a connector that needs only a handful does not present all of them as equally relevant. A group with a green tick is fully configured.
---
# 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.openiam.com/connector-configuration/2-configparam.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.
