> 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/getting-started/setup-sso-and-automatic-user-provisioning.md).

# Setup SSO and automatic user provisioning

### SAML Single Sign-On Setup

FenixPyre offers two flexible options for setting up SAML-based Single Sign-On (SSO), allowing you to integrate with your organization’s existing identity provider:

1. **Azure Active Directory (Entra ID) SSO Integration**

Admin can set up SAML SSO using **Azure Active Directory (Entra ID)**. This method integrates FenixPyre with your Azure AD instance, enabling secure and centralized access management for your organization’s users.

Follow through this guide to [setup Azure Active Directory](/fenixpyre-for-admins/admin-dashboard/identity-and-provisioning/saml-single-sign-on-sso-setup/set-up-saml-sso-with-azure.md).

2. **Okta SSO Integration**

FenixPyre seamlessly integrates with **Okta** for SAML-based authentication. With Okta, you can manage user access across all your applications with ease, while leveraging Okta’s robust security and user management features.

Follow through this guide to [setup Okta SSO Integration](/fenixpyre-for-admins/admin-dashboard/identity-and-provisioning/saml-single-sign-on-sso-setup/set-up-saml-sso-with-okta.md).

### Automatic User Provisioning Setup (SCIM Provisioning)

Using SCIM, you can automatically provision and de-provision users in your identity provider (IdP).

Follow through this guide to [setup SCIM provisioning](/fenixpyre-for-admins/admin-dashboard/identity-and-provisioning/scim.md).


---

# 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/getting-started/setup-sso-and-automatic-user-provisioning.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.