> 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/identity-and-provisioning/scim.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
