---
description: >-
  Single Sign-On (SSO) offers the ability for an external service (e.g.
  Microsoft Active Directory, Google) to authenticate your organization's users
  to Pitchly.
---

# Single Sign-On Overview

_Note: Single Sign-On is not available by default in Pitchly's plans. It is negotiated and configured on a plan-by-plan basis._

## Single Sign-On Process Flow

![](https://295169749-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-panoVV706RAXpUlzW%2F-M3RXfPKCv-KF7URYbFr%2F-M3RXlMLuXugYjSlNQmo%2FPitchly%20SSO%20Overview.png?alt=media\&token=d8f0dbba-1aae-4a71-bf45-a9f6fa64db20)

1. User visits Pitchly sign-on page and provides their email address.
2. SSO is detected for user and they are redirected to their organization's login page.
3. Login credentials (email/username and password) are authenticated against their organization's identity provider/authentication service.
4. SSO service passes back a signal to Pitchly that a successful sign-on/authentication has occurred.
5. The user is automatically logged into and placed in the Pitchly application.

## Troubleshooting

If your company's users encounter problems using your SSO service to authenticate to Pitchly, there are a few things to keep in mind to help troubleshoot.

### 1) The Email Address _Must_ Match All The Way Through

Pitchly maintains a single e-mail address for each user in our system and that e-mail address _must_ match at all points in the SSO process outlined above.

Example: User whose email is **pitchlyuser@yourcompany.com**

* Step 1 - Pitchly sign-on screen: User enters **pitchlyuser@yourcompany.com**&#x20;
* Step 2 - Your company's SSO: User enters **pitchlyuser@yourcompany.com** (and password)
* Step 5 - After successful SSO authentication, Pitchly expects to receive from your SSO provider: **pitchlyuser@yourcompany.com**

### 2) The Email Domain _Must_ Be Listed in Pitchly

In addition to a single email address for each Pitchly user, a list of email domains eligible for SSO is also stored within your company's Pitchly settings. _(In the example above, the email domain is: **yourcompany.com**)_

The SSO email domain list is created and maintained by Pitchly tech support staff and is intended as an added layer of security. Any new or changed email domains within your organization must be communicated to us to prevent SSO sign-in errors.

**Note:** Microsoft's cloud-based offerings sometimes put their own branding in the email domain, e.g. **yourcompany.**_**onmicrosoft**_**.com** - While either domain at the end of an email address may authenticate within your SSO system, it will _not_ ultimately match the final Step 5 above, where Pitchly is expecting **pitchlyuser@yourcompany.com**.

In this scenario, both checks on the full email address itself _and_ the email domain with "onmicrosoft" in it would fail to authenticate with Pitchly (Step 5).

## Screenshots for Microsoft AD

![Step 1 - Pitchly Login Screen](https://295169749-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-panoVV706RAXpUlzW%2F-M3IEiay26QWOcQE3CMe%2F-M3IRP81BQ-Vx5qHvIyr%2FScreenshot%20from%202020-03-25%2015-03-58.png?alt=media\&token=fed5cecb-ab60-46dc-a659-e5dbe2dc9f4c)

![Step 2.1 - Your company's SSO prompt](https://295169749-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-panoVV706RAXpUlzW%2F-M3IEiay26QWOcQE3CMe%2F-M3IRbusr_8wETGSpwz-%2FScreenshot%20from%202020-03-25%2015-04-08.png?alt=media\&token=a9d511ee-71e0-46ee-b753-2bc543522db6)

![Step 2.2 - User provides their email & password to your SSO](https://295169749-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-panoVV706RAXpUlzW%2F-M3IEiay26QWOcQE3CMe%2F-M3IRnk3iPjf4nR8EJCE%2FScreenshot%20from%202020-03-25%2015-05-49.png?alt=media\&token=1f1a8265-2459-4e34-a2b7-91ece5f719fb)
