CrowdComms currently supports SSO via the SAML2 standard. This is an enterprise-grade industry standard to allow users to authenticate between Identity Providers (IDPs) and Service Providers (SPs). The CrowdComms platform is a Service Provider and examples of IDPs include Microsoft Active Directory, OneLogin, Okta and others.


Q: Do all the delegates still need to be registered on the site as usual?
A: No if they’re logging in via their company’s directory. With SSO, the user’s basic information such as First name, Last name, Email, and Phone number will be auto-populated in the event app.


Q: My event will consist of delegates from my own company and speakers from outside the company, can I still use SSO?
A: Yes, delegates from within the company who has been authenticated will be able to utilise the SSO function. The speakers from outside the company will be able to log in to the event app using their username and password.


Q: Not everyone in my company’s Active Directory will be invited to my company’s event, can I still use SSO and tailor only the relevant people to have access to the event app?
A: Yes, once your business IT contact has set up the SAML2, you can work with them to decide who from your company should get delegate access to the event app.



Single sign-on (SSO) is an authentication process that allows a user to use one set of login credentials, for example, a username and password, to access multiple applications.


SSO helps clients and their users with the challenge of maintaining the different credentials for different applications separately which streamlines the process of signing on without the need to re-enter the password. With SSO end-users time and efforts get minimized as they don’t need to constantly sign in and out separately into multiple applications.


Setting up SSO must be done by the client's IT department or technical personal. The setup will involve authenticating the Identity Prover (IDP) i.e., the client with the Service Provider (SP) i.e., Crowdcomms event platform.








How does SSO workSSO works based upon a trust relationship set up between an application, known as the service provider, and an identity provider, like OneLogin. ... In SSO, this identity data takes the form of tokens that contain identifying bits of information about the user like a user's email address or a username.

How to set up saml2-compatible identity providers...

Getting the client set up

Provide them the following details

They should come back with a metadata URL that can be imported


Field Mapping


Logging into Front End


Manual Set Up

**Copy the Field Mapping steps from Above**

**Repeat Adding a New User to the App through One Login steps from Above**

**Repeat the Logging into Front End steps from Above**

Branding the Login Page with SSO...

The Front End Login page can be branded with unique text and/or with a logo through CMS.