> For the complete documentation index, see [llms.txt](https://docs.fenixpyre.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/identity-and-provisioning/scim.md).

# SCIM

**SCIM (System for Cross-Domain Identity Management)** is an industry-standard framework designed to streamline and automate the management of user identities across different systems and applications. SCIM provisioning enables seamless and secure user lifecycle management by automating the processes of creating, updating, and deactivating user accounts across various services, reducing the administrative burden and the potential for errors.

FenixPyre integrates with leading identity providers like **Azure Active Directory** and **Okta**, allowing for efficient and automated user provisioning and de-provisioning. With this integration, your organization can ensure that user data remains consistent, accurate, and up-to-date across all systems, while also maintaining strict access control and security compliance.


---

# 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.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/identity-and-provisioning/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.
