> ## Documentation Index
> Fetch the complete documentation index at: https://docs.niteshift.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Single sign-on

> Connect your identity provider to Niteshift, let members opt in, then require SSO for your organization.

Single sign-on (SSO) lets members sign in to Niteshift through your identity provider (Okta, Entra
ID, Google, or any SAML or OIDC provider) instead of GitHub. Your members' tasks, history, and settings stay on the same accounts when they
switch.

> [!NOTE]
>
> SSO is in early access. Contact [support@niteshift.dev](mailto:support@niteshift.dev) to enable it for your organization.

## Before you start

* You're an admin of the Niteshift organization. Only admins see SSO setup.
* You can add a DNS TXT record for your company domain, or work with someone who can.
* You can create an application in your identity provider, or work with someone who can.

SSO settings live under **Single sign-on** on the
[Members settings page](https://niteshift.dev/organization/settings/members#sso).

## Set up SSO

![Single sign-on setup with the domain verified, Connect your identity provider as the current step, and Test sign-in asking a personal-email admin to confirm a work email.](https://mintcdn.com/niteshift/hAK6pvpiIIw19n72/images/sso/setup-checklist.png?fit=max\&auto=format\&n=hAK6pvpiIIw19n72\&q=85\&s=fc438aab89a2d3c831422ba06150d181)

**1. Verify your domain**

Click **Verify domain**. A setup portal opens and walks you through adding a DNS TXT record. Once the record is confirmed, return to **Single sign-on** in Niteshift. The domain shows as verified.

**2. Connect your identity provider**

Click **Connect** and choose your provider in the setup portal. It gives provider-specific instructions for SAML and OIDC, including the values to copy into your identity provider.

![Setup portal asking you to select your identity provider, with Okta, Entra ID, Google, and custom SAML or OIDC options.](https://mintcdn.com/niteshift/hAK6pvpiIIw19n72/images/sso/workos-select-provider.png?fit=max\&auto=format\&n=hAK6pvpiIIw19n72\&q=85\&s=d174d9717da7800f7f9f204e94fb56b0)

**3. Test sign-in**

Click **Sign in with SSO** and sign in through your identity provider. This step completes only after your own SSO sign-in succeeds.

If your Niteshift account is attached to an email outside the verified domain (a personal address, for example), enter your **Work email** and click **Email me a code**. Confirm the code, then sign in with SSO. Your work email attaches to your existing Niteshift account, so you don't end up with a second account.

![Test sign-in step asking for the code emailed to the work address, with a Confirm and sign in with SSO button.](https://mintcdn.com/niteshift/hAK6pvpiIIw19n72/images/sso/work-email-code.png?fit=max\&auto=format\&n=hAK6pvpiIIw19n72\&q=85\&s=a12c2cede8b96b32f3e16c46e98e92a8)

**4. Let members opt in**

Click **Let members opt in**. Members can switch from **Settings › Connections** whenever they're ready.

**5. Require SSO**

When everyone is ready, click **Require SSO**. The button stays disabled until the connection is active on a verified domain, every member is set up for SSO, and you have signed in with SSO.

## GitHub access

By default, members who sign in with SSO still connect their personal GitHub account in
**Settings › Connections**, so commits and pull requests are created as them. To let members without
a GitHub connection start tasks as the Niteshift [GitHub App](https://docs.niteshift.dev/interfaces/github.md), turn off
**Require personal GitHub to start tasks** under **Single sign-on**.

> [!WARNING]
>
> With this setting off, members without a GitHub connection have full access to every repository
> connected to the Niteshift GitHub App.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.