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

# Single Sign-On (SSO)

Datalogz supports self-service SAML single sign-on, so an administrator can connect your identity provider directly, without a support ticket. This is part of Organizational Setup.

{% hint style="info" %}
Configuring SSO requires the **Sys Admin** permission. If you do not see the SSO settings, ask an administrator with that permission to complete the setup.
{% endhint %}

### How to configure SAML SSO

1. Go to **Settings > Single Sign-On**.
2. Click **Configure SSO**.
3. Enter the SAML details from your identity provider: the **Sign-in URL**, **Issuer / Entity ID**, and the **signing certificate**.
4. Copy the Datalogz **Assured Consumer Service (ACS) URL** and **Entity ID** into your identity provider's SAML application.
5. Click **Save** to store the configuration, then use **Test connection** to confirm a successful round trip before rolling it out to users.

### Passwordless email sign-in

For users who are not signing in through SSO, Datalogz offers a passwordless email login. The user enters their email, receives a one-time code, and enters it to sign in. There is no password to set, store, or reset.

### Login screen announcement banner

Administrators can show a configurable announcement banner on the login screen, for example to communicate planned maintenance or a change to sign-in. The banner is driven by configuration and appears to every user before they sign in.

For questions or help with this setup, contact <support@datalogz.io>.


---

# 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.datalogz.io/guides/single-sign-on-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.