> For the complete documentation index, see [llms.txt](https://docs.peig.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peig.io/welcome-to-peig-documentation/deployment-guides/other-applications.md).

# Other applications

{% hint style="warning" %}
Detailed per-application guides are coming soon. The steps below cover the general process for any SAML or OIDC-compatible application.
{% endhint %}

Most modern SaaS applications support SAML 2.0 or OIDC — which means they can be connected to Peig without any custom development.

## Connecting a SAML application

You will need to exchange configuration details between Peig and your application.

**From Peig → your application:**

Open **Configuration → SAML IDP Info** in your Peig workspace and provide these values to your application:

* IDP Entity ID
* Sign-In URL (POST mode)
* Sign-Out URL
* IDP Certificate

**From your application → Peig:**

In your Peig workspace, open **Configuration → Add New Provider** and select the SAML template. Enter the following values from your application:

* Entity ID (SP Entity ID / Audience URI)
* Assertion Consumer Service (ACS) URL

Once both sides are configured, click **Validate and Add**. The application will appear as an Active Provider in your workspace.

## Connecting an OIDC application

Peig supports OpenID Connect (OIDC) for applications that use this protocol. Contact your Peig account manager for OIDC connector setup.

## Assigning access to users

After adding a provider, go to **Users & Access**, open each user's profile, and toggle the application on under their **Services** list.

For SAML applications that require a per-user identifier, click **Add Provider ID** and enter the user's identifier for that application — typically their email address.