---
title: "Other SAML providers"
description: "Connect Okta, Google Workspace, or another SAML 2.0 identity provider to Davner."
canonical_url: "https://davner.com/docs/organization/sso/other-saml-providers"
type: "doc"
---

Source: https://davner.com/docs/organization/sso/other-saml-providers

Davner supports any identity provider that uses SAML 2.0, including Okta and Google Workspace. Your IT administrator creates a SAML application for Davner, chooses who has access, and connects it to Davner. If you use Microsoft Entra, follow the [illustrated Entra guide](https://davner.com/docs/organization/sso/microsoft-entra) instead.

## Before you start

- Sign in to Davner as an **admin** or **owner**, open **Organization → Settings**, and select [Set up SSO](https://davner.com/app/organization/sso).
- Work with your IT administrator to create the application in your identity provider.
- Keep Davner's SSO settings open while you work in your identity provider.

## Connect your identity provider

1. **Enter your email domain in Davner**

    Enter your team's email domain in the connection's **Domain** field. Separate multiple domains with commas if they use the same identity provider. Do this before copying the **Reply URL (ACS URL)** into your identity provider.

2. **Create a SAML application**

    In your identity provider's admin console, create a custom SAML 2.0 application and name it **Davner**.

3. **Enter Davner's values**

    Copy the values displayed for your connection in Davner's SSO settings into the matching fields. Identity providers use different names for them:

    | Value from Davner | Common names in identity providers |
    | --- | --- |
    | **Identifier (Entity ID)** — `https://davner.com` | Entity ID, Audience URI, SP Entity ID |
    | **Reply URL (ACS URL)** | ACS URL, Assertion Consumer Service URL, Single sign-on URL |

    Copy the full Reply URL shown for this connection. Each connection has its own.

4. **Send the user's email address**

    Set the **Name ID format** to **EmailAddress** and the **Name ID** to the user's primary work email address.

    To show each person's name in Davner, also send these attributes:

    | Attribute name | Value |
    | --- | --- |
    | `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname` | First name |
    | `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname` | Last name |

    If you don't send them, Davner shows the email address in place of the name.

    Davner requires signed assertions. Use SHA-256 if your identity provider asks for a signature algorithm.

5. **Choose who should have access**

    Assign the users or groups that need Davner to the application.

6. **Copy the identity provider's metadata into Davner**

    Davner reads the signing certificate, sign-in URL, and issuer from your identity provider's SAML metadata.

    - If your identity provider shows a **metadata URL**, paste it into **App Federation Metadata URL** on the **Metadata URL** tab. The URL must use `https://`.
    - Otherwise, download the metadata XML file, open it in a text editor, and paste its contents on the **Paste XML** tab.

7. **Save the connection and verify your domain**

    Select **Save and request activation**. You'll see **Pending activation**. [Contact us](https://davner.com/contact) so we can verify ownership of the domains. We'll let you know when the connection is active, usually within a business day.

8. **Test with an assigned team member**

    Once Davner shows **SSO is active**, have an assigned team member sign in at [davner.com/login](https://davner.com/login) using an email address at a verified domain.

    Davner creates their account when they first sign in and adds them to your organization as a **Member**.

## Provider-specific tips

**Okta**

Create an app integration with **SAML 2.0** as the sign-in method. Enter the Reply URL in **Single sign-on URL** and the Identifier in **Audience URI (SP Entity ID)**. Set **Name ID format** to **EmailAddress** and **Application username** to **Email**.

After saving, copy the **Metadata URL** from the application's **Sign On** tab.

**Google Workspace**

In the Google Admin console, add a custom SAML app. Download the **IdP metadata** file and paste its contents on Davner's **Paste XML** tab.

Enter the Reply URL in **ACS URL** and the Identifier in **Entity ID**. Set **Name ID format** to **EMAIL** and **Name ID** to **Primary email**. Map **First name** and **Last name** to the attribute names above.

Turn the app on for the users or organizational units that need Davner.

## Connect another identity provider

If your organization uses more than one identity provider or tenant, select **Add another connection** in Davner and repeat these steps. Each connection has its own domains and Reply URL, so copy the values shown for the connection you're setting up.