> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/reference-manual/v3.44.5/built-in-connectors/scim.md).

# SCIM

The SCIM connector for Elimity Insights fetches users and groups from a SCIM server so you can keep in control of your environment. Follow the instructions below to set up the connector for your environment.

## 1. Creating a dedicated read-only user

As usual, we recommend creating a dedicated read-only user for this connector. Exact instructions depend on the software serving the SCIM API, but in general this connector only requires read access to users and groups. We also recommend generating a secure password for this new user. Note down both the username and password for later use. Alternatively you can also generate a bearer token with similar permissions.

## 2. Creating a source in Elimity Insights

In Elimity Insights you can now create a new SCIM source providing the following configuration options:

<table data-full-width="true"><thead><tr><th>Configuration option</th><th>Description</th></tr></thead><tbody><tr><td>Base URL</td><td>URL of your SCIM server (e.g. <code>https://api.slack.com/scim/v2</code>).</td></tr><tr><td>Username</td><td>The username you noted down in step 1, or leave empty if you want to authenticate with a bearer token.</td></tr><tr><td>Password</td><td>The password or bearer token you generated in step 1.</td></tr></tbody></table>


---

# 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.elimity.com/reference-manual/v3.44.5/built-in-connectors/scim.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.