How to enable SSO (Single-Sign On) for your Attendees in an Organisation

Pre-requisite: 

Your Pigeonhole organisation would need to have SSO for attendees set up and enabled. Check out the documentation for your IDP service to navigate the set up:

• Setting up an Organisation Attendee SSO on Auth0
• Setting up an Organisation Attendee SSO on Okta
• Setting up an Organisation Attendee SSO on Google Workspace
• Setting up an Organisation Attendee SSO on Microsoft Entra ID (Azure Active Directory)

Example of an SSO login screen your attendees will see if SSO is enabled for your attendees

SSO (Single Sign-on) for attendees (also known as “attendee SSO”) allows you to restrict access to Pigeonhole Live events to only those in your organisation. This helps prevent unauthorised access to information shared during your event and verify each attendee’s identity to enforce accountability. 

When you set up SSO to verify attendees' access to your Pigeonhole Live events, we will work with your Identity Provider (IdP) to import your attendees' name and email address. Once imported, attendees will be verified using that information and will not be able to alter the information by themselves. 

You can find attendees’ profiles under your Pigeonhole Insights once they access an event on Pigeonhole Live.

Configuring attendee SSO for your organisation
 

Step 1: Click on your Organisation selection list from the top-left corner of the interface and select your Workspace name from your Organisation selection list.

Step 2: Click on your Workspace selection list from the top-left corner of the interface and select the Workspace Settings of your selected workspace.

Step 3: Select the Attendee SSO profile which you added for your workspace from organisation settings and Save to confirm your selection.

Step 4 (optional): 

When SSO is enabled, only organisational users are able to enter the Pigeonhole. Allow attendees to access through Registrant profiles is an optional setting that is recommended for these scenarios:

1. Hybrid event: Your event is hybrid and the organiser would like on-site users to login to Audience Web App via Pigeonhole SSO, and virtual attendees to access the Audience Web App via a third party platform with its own SSO.
2. Event with both organisational and external users: Your event has an external team working with the event. Organisational attendees are logging in via Pigeonhole SSO, and the external team is logging in with their own email domains to help manage the event. 

Scenario 1: Hybrid event

When enabled, this optional setting will take attendees’ name and email information, if available, from the third party platform that your Pigeonhole is embedded in, and pass that through to the Audience Web App. Your attendee will then be logged in with their profile on the embedded Audience Web App.  

Both virtual and in-person attendees will then be able to use SSO to login and create a profile in Pigeonhole with their details. 

The attendee experience will be as follows: 

• Virtual attendee: Enters 3rd party platform and is prompted with 3rd party platform SSO login. Submits login details successfully and is logged into embedded Pigeonhole Audience Web App with profile.
• In-person attendee: Scans QR code onsite and is prompted with SSO login on Pigeonhole event entry page. Submits login details successfully and is logged into Pigeonhole Audience Web App on their device with profile.

There are security implications to using this setting. You should only enable it if you fully understand and accept the associated risks. Enable this setting only if you are using a trusted third-party platform or a secure, reliable login method.

Scenario 2: External event team 

When enabled, an additional method to log in to the event will appear on the Audience Web App. Pre-registered members then can use this to enter their attendee codes and sign-in to the event. It is most useful for events teams, who may not share the same domain as the organisation, but still require the ability to log in to the Audience Web App on-site. 

Ensure that the events teams have been pre-registered as registrants, and have access to their attendee codes, for smooth facilitation. 

This will complete the configuration for the Organisation Attendee SSO setup. Now you can Run link (Audience Web App) which will redirect attendees to access Attendee SSO of the Identity Provider of your choice.

Step 5: Click on the Save button to save the changes. 

Configuring attendee SSO for your event

When you set up your event, you will need to enable and select an SSO profile for each Pigeonhole.

Step 1: In your event, click on the Attendees tab from the top menu bar.

Step 2: Click on the Security tab from the menu bar.

Step 3a: Select the Attendee SSO profile which you added for your workspace from organisation settings and and Save to confirm your selection.

Step 3b: When enabled, this optional setting will take attendees’ name and email information from the third party platform that your Pigeonhole is embedded in, and pass that through to the Audience Web App. Your attendee will then be logged in with their profile on the embedded Audience Web App.  

This optional setting  is recommended when you:

1. Are running a hybrid event with both online and in-person attendees, and
2. Use a 3rd party platform with its own SSO login, and want to embed a Pigeonhole's Audience Web App within that platform 

This setting allows both virtual and in-person attendees to use SSO to login and create a profile in Pigeonhole with their SSO details. 

When SSO is enabled for both, the attendee experience will be as follows: 

• Virtual attendee: Enters 3rd party platform, prompted with 3rd party platform SSO login. Submits login details successfully and is logged into embedded Pigeonhole Audience Web App with profile.
• In-person attendee: Scans QR code onsite, faces SSO login on Pigeonhole event entry page. Submits login details successfully and is logged into Pigeonhole Audience Web App on their device with profile.

There are security implications to using this setting. You should only enable it if you fully understand and accept the associated risks. Enable this setting only if you are using a trusted third-party platform or a secure, reliable login method.

This will complete the configuration for the Organisation Attendee SSO setup. Now you can Run link (Audience Web App) which will redirect you to access Attendee SSO of the Identity Provider of your choice.