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

# Single sign-on

Bunny doesn't hold any user passwords. The default way a user signs in is by entering their email on the login page after which they will receive an email with a magic link that signs them in.

An even more secure and user-friendly way to sign users into Bunny is using single sign-on. Bunny supportes SAML SSO and can easily be set up to work with Okta, OneLogin or Google. See the [SSO configuration guides](/guide/advanced-guides/single-sign-on.md) for this.

<figure><img src="/files/06eqdfB2PP6CiDDKbwC5" alt=""><figcaption><p>Single sign-on settings</p></figcaption></figure>

Note that you can always configure a user to bypass SSO using the **Always sign in via email login link** on the user. This is useful when you have contractors or similar who may not be configured in your identity provider.

### Enabled

You can temporarily disable SSO disabling this setting. This will force users to sign in with an email link.

### SSO mode

Once SSO has been configured, Bunny can be configured to handle sign-in in two ways.

* **Always prompt users** - Users will be prompted to enter their email address and if SSO is required, they will be redirected to the identity provider.
* **Automatic redirect** - This will redirect all users without a valid session to the identity provider immediately when they hit Bunny's login page.

If you are using Bunny in conjunction with Salesforce, the second setting is recommended as it will reduce friction related to signing in.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bunny.com/guide/tour/settings/single-sign-on.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.