---
title: "Sign in with SSO"
description: "Sign in through your company's Okta or OpenID Connect provider by entering your work email on the Pyn sign-in page."
sidebar:
  order: 2
area: account
feature: sign-in
appPath: /sign-in
lastVerified: 2026-10-22
version: "2026-10-16"
audience: employee
screenshots:
  - id: account-sign-in-sso
    caption: After Continue with SSO, Pyn asks for the work email it uses to find your identity provider.
related:
  - account/sign-in
  - integrations/sso
  - getting-started/roles-and-permissions
intercom:
  - id: "16838066"
    title: Enabling Single Sign On (Pyn 2)
    url: https://intercom.help/pyn/en/articles/16838066-enabling-single-sign-on-pyn-2
    note: draws on
  - id: "16729319"
    title: Sign into Pyn (Pyn 2)
    url: https://intercom.help/pyn/en/articles/16729319-sign-into-pyn-pyn-2
    note: draws on
---

Your company has connected its identity provider to Pyn, and you want to sign in the same way you sign in to everything else at work. You give Pyn your email address; Pyn looks up the provider that owns that domain and hands you to it.

## Before you start

- An admin has installed the **Single Sign-On** integration for your workspace. [SSO](https://support.pynhq.com/integrations/sso/) explains how.
- You know your work email address. Pyn uses its domain, such as `example.com`, to find the right provider.

## Steps

1. Open `https://app.pyn.ai/sign-in` and select **Continue with SSO**.

2. On **Enter your email address**, read "Enter your work email address and you will be taken to your organisation's single sign-on provider." Type your address in **Email**.

![After Continue with SSO, Pyn asks for the work email it uses to find your identity provider.](https://support.pynhq.com/media/account/sign-in/account-sign-in-sso.png)

3. Select **Continue**. The field locks while Pyn looks the domain up.

4. Sign in at your identity provider when it opens. It returns you to Pyn.

> **Note:** Your role in the workspace can come from your identity provider. When the admin has mapped provider groups to Pyn roles, Pyn gives you the highest role of any group you are in each time you sign in. See [Roles and permissions](https://support.pynhq.com/getting-started/roles-and-permissions/).

## What you should see

The **Signing In** screen, then [Home](https://support.pynhq.com/home/) or **Switch Workspace** if you belong to more than one workspace.

## Troubleshooting

- **"Email not found"** appears under the field. No workspace has claimed that email domain for single sign-on, or the address is malformed. Check the spelling, or sign in with [Google or Microsoft](https://support.pynhq.com/account/sign-in/sign-in-with-google-or-microsoft/) or [a magic link](https://support.pynhq.com/account/sign-in/sign-in-with-a-magic-link/) and ask your admin whether SSO is connected.
- **"Something went wrong, please try again"** appears. The lookup failed on the network. Select **Continue** again; **Restart** returns you to the four buttons.
- **Your provider signs you in but Pyn shows no workspace.** Pyn does not create users on first sign-in through SSO. An admin still has to invite your address, or you need to be in a provider group that is mapped to a role.

## Related

- [Sign in](https://support.pynhq.com/account/sign-in/) for the other options and what happens after sign-in.
- [SSO](https://support.pynhq.com/integrations/sso/) for how an admin connects Okta or an OpenID Connect provider and maps groups to roles.
- [Roles and permissions](https://support.pynhq.com/getting-started/roles-and-permissions/) for what each mapped role can do.

## Related Intercom articles

- [Enabling Single Sign On (Pyn 2)](https://intercom.help/pyn/en/articles/16838066-enabling-single-sign-on-pyn-2) — draws on
- [Sign into Pyn (Pyn 2)](https://intercom.help/pyn/en/articles/16729319-sign-into-pyn-pyn-2) — draws on