> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/vendor-platform/customer-accounts/single-sign-on-sso-customer-accounts.md).
# Single Sign On (SSO) - Customer Accounts
Set up a dedicated SSO provider for a specific Customer Account, enabling users within that account to authenticate through their own identity provider.
Each Customer Account can be configured with its own SSO provider, enabling users within that account to authenticate through their own identity infrastructure rather than using LicenseSpring's default authentication.
{% hint style="info" %}
This page covers SSO configuration at the Customer Account level, which applies only to users within that specific account. For company-wide SSO setup, see [Single Sign-On (SSO)](/common-scenarios/single-sign-on-sso.md).
{% endhint %}
### Adding an SSO Provider
To configure SSO for a Customer Account, open the account and navigate to the **Single Sign On** tab, then click **Add provider**.
The following provider types are supported:
* **SAML:** Upload the provider metadata `.xml` file and set a default redirect URI
* **Google:** Requires a Name, Client ID, and Client Secret
* **Apple:** Requires a Service ID, Key ID, Team ID, and `.p8` key file
* **OpenID Connect (OIDC)**: Requires a Client ID, Client Secret, and well-known configuration URL
Fill in the required fields based on your selected provider type and click **Confirm** to save.
### Additional Options
**Require email verification on first SSO login** when enabled, users logging in via SSO for the first time will be required to verify their email address before gaining access.
**Multiple Redirect URIs** : if you need to support multiple redirect URIs, ensure you are on the latest SDK version. See the SDK[ documentation](/sdks/introduction.md) for details.
---
# 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.licensespring.com/vendor-platform/customer-accounts/single-sign-on-sso-customer-accounts.md?ask=&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.
