> For the complete documentation index, see [llms.txt](https://docs.b2b-sellers.com/b2b-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2b-sellers.com/b2b-platform/user-guide/available-add-ons/single-sign-on.md).

# Single Sign-On (SSO)

Letting customers, employees and sales representatives log in with an external identity provider

Single Sign-On lets the users of your shop log in with an account they already have on another platform. Once configured it is available to all employees of customers, to sales representatives, and to B2C customers of your shop.

## Enabling the add-on

Make sure the add-on is activated in the license settings.

![](https://3555939725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7trivXBQb3doKIrPW2i%2Fuploads%2F1xquI26uwJfNFNViVKZx%2Fsso-license.png?alt=media)

Then open **Single Sign-On settings** in the B2B settings.

![](https://3555939725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7trivXBQb3doKIrPW2i%2Fuploads%2FQPVgNpfXkQAKUh8CNGwE%2Fsso-settings-menu.png?alt=media)

This view lists all existing provider configurations, lets you manage them, and lets you add further providers.

![](https://3555939725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7trivXBQb3doKIrPW2i%2Fuploads%2FgQjvRm1s6Kkd6i5rdkom%2Fsso-provider-list.png?alt=media)

## Adding a provider

Click **Add provider** and fill in every field of the dialog.

![](https://3555939725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7trivXBQb3doKIrPW2i%2Fuploads%2F6SIERHpfVnrvPxJDvxip%2Fsso-add-provider.png?alt=media)

| Field                 | Meaning                                                   |
| --------------------- | --------------------------------------------------------- |
| Name                  | The public display name shown on the login page.          |
| Active                | Whether the option is offered to users on the login page. |
| Type                  | The protocol used. Auth0 is currently supported.          |
| Domain                | The domain to authenticate against.                       |
| Client ID             | The client ID of that domain.                             |
| Client secret         | The client secret of that domain.                         |
| Allowed callback URLs | The URLs required by the Auth0 application.               |

![](https://3555939725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7trivXBQb3doKIrPW2i%2Fuploads%2FLh84YLfwLh4ZimE7QxK5%2Fsso-login-button.png?alt=media)

## How logging in works

1. The user opens the login screen and clicks the SSO link.
2. The user authenticates on the external platform.
3. The user is redirected back to the shop and is logged in automatically as the account whose e-mail address was used.

## FAQ

* **How long does the session persist?**
  * The session in the shop lasts as long as the session exists on the provider's side. No repeated login in the shop is required during that time.
* **Can new accounts be created through SSO?**
  * No. Only existing accounts with a matching e-mail address can be logged into. If the e-mail address is not associated with any account, an error message is shown.
* **Does SSO disable the password login?**
  * No. Users can still log in with their credentials instead of using SSO.


---

# 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.b2b-sellers.com/b2b-platform/user-guide/available-add-ons/single-sign-on.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.