> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/global-settings/security/identity-providers-sso/logging-in-with-sso.md).

# Logging In With SSO

## ![](https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FSxcnKlaJKPzDqONWoDNv%2FSummary2-Small-Icon.svg?alt=media\&token=5e3253d0-a069-4ba5-9c06-83c70bd0b21d) Overview

Flosum Cloud Apps provides enhanced security and centralized access control through Single Sign-On (SSO) across its applications. This feature allows users to log in seamlessly with their corporate credentials. If a valid Identity Provider is enabled on your tenant, follow the instructions in this article to access the SSO login screen.

For instructions on creating and managing an Identity Provider for your SSO, see the following articles.

* [Adding an Identity Provider (SSO)](/global-settings/security/identity-providers-sso/adding-an-identity-provider-sso.md)
* [Managing Identity Providers (SSO)](/global-settings/security/identity-providers-sso/managing-identity-providers-sso.md)

## Log In With SSO

{% hint style="info" %}

#### Tenant Name Log In

SSO is only available when logging in with your **Tenant Name**.
{% endhint %}

{% hint style="warning" %}

#### No SSO Button

If the SSO button you created with the Identity Provider is missing from the tenant login screen, there may be an issue with the provider details. Verify that the Identity Provider configuration matches the SSO credentials.
{% endhint %}

1. Navigate to the Flosum Cloud App Login in your browser.
   1. [https://login.flosum.app](https://login.flosum.app/)
2. Click **Use tenant name**.&#x20;

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FhuyfCJS4UJWN33Y3reU9%2FAuth0Setup-S03-01.png?alt=media&amp;token=1d031449-707e-4d2f-b20f-92cc30bd8ec0" alt="" width="375"><figcaption></figcaption></figure></div>
3. Click the **Region** of the tenant you want to log in to.&#x20;

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FKjUIn6NH3DAkX3RXMBBX%2FLoggingInWithSso-Login-02.png?alt=media&amp;token=aba1cbfc-83ca-4ecf-839d-1268ef2d36fc" alt="" width="375"><figcaption></figcaption></figure></div>

{% hint style="info" %}
If unsure about your tenant's region, please contact your system administrator for assistance.
{% endhint %}

4. Enter the name of the tenant in the **Tenant Name** textbox.
5. Click **Continue**.&#x20;

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FHSnLBGBDsxA1fExhmw6b%2FLoggingInWithSso-Login-03.png?alt=media&amp;token=f39a0fab-4f82-417f-ad65-4f6e6865f9c0" alt="" width="375"><figcaption></figcaption></figure></div>
6. Click the SSO button created by your system administrator. SSO buttons appear below the **LOGIN** button.

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FwvEUmShu3DEspSdiTtMl%2FLoggingInWithSso-Login-04.png?alt=media&amp;token=b8ed14c6-fdcb-41c4-aefd-e79f5dde2163" alt="" width="375"><figcaption></figcaption></figure></div>

{% hint style="info" %}
You may see multiple SSO buttons, and their labels may differ from the screenshot above. If you are unsure which button to click, ask your system administrator.
{% endhint %}

7. Complete the login with your SSO provider.


---

# 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.flosum.com/global-settings/security/identity-providers-sso/logging-in-with-sso.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.
