1. Accessing SSO configuration
SSO can be enabled once Contacts are available on your account.
To access it:
Dashboard → Contacts tab → SSO configuration
⚠️ Only an Eventmaker project manager (CSM) can activate and configure SSO for your account.
2. Configure your event SSO
This SSO is used to authenticate your attendees and exhibitors on the following areas:
Registration form
Personal area
Website Builder
KeepTrack mobile app (depending on configuration)
2.1 Domain name
You can choose:
an Eventmaker subdomain (
exemple.eventmaker.io),or your own domain (
login.evenement.fr).
2.2 Terms of use
If your users must accept Terms of Use:
add the document URL,
the link will be displayed before account creation.
2.3 Visual customization
Your login page can be fully branded:
favicon
logo
banner
primary color
background color or image
Goal: an SSO 100% aligned with your visual identity.
2.4 Password security
⚠️ Too high a security level can harm the user experience.
👉 Adapt it according to:
the sensitivity level of the data collected,
the audience concerned (public trade show vs corporate event).
3. Applications using SSO
From the Applications tab, choose where your SSO should be applied:
On an Eventmaker site: simply add your site to the SSO.
On an external site you can use our SSO mechanism; you will need to provide:
application name
post-login redirect URL
multi-application management possible
This enables centralized login across all your event tools.
4. External sign-in providers (Google, LinkedIn, Facebook)
Eventmaker allows using external identities to streamline the user experience through authentication via:
Google
LinkedIn
Facebook
To configure them, your CSM will need:
application name
logo
SSO domain
privacy URL
Redirect URI provided by Eventmaker
provider ID + secret key
Important specifics:
The user is created with the email provided by the provider.
If the user changes their email in Eventmaker, their social login remains valid.
If a contact already exists with a different address, they can log in via SSO if the prefilled email matches.
Provider data never overwrite existing Eventmaker data.
LinkedIn example:
5. SAML provider (the most secure)
SAML is recommended for sensitive organizations (international groups, banks, institutions…).
To activate a SAML, you must provide:
NameID format
SSO login URL
logout URL
certificate
certificate identifier
Then: map the SAML attributes to the Eventmaker participant fields.
Eventmaker also allows importing SAML metadata directly.
6. Enterprise SSO (SSO for internal Eventmaker users)
This feature allows companies to use their corporate authentication system to connect their teams to the Eventmaker back-office.
Main benefits:
password rules are managed by the company
when an employee leaves the company → they automatically lose access to Eventmaker
enhanced compliance with internal security policies
centralized access management
ability to trace logins in the company’s internal tools
6.1 Creating an Enterprise SSO
This configuration is available only to Eventmaker super-admins.
Required configuration:
internal name
one or more domains (e.g.:
company.com)exceptional email addresses (optional)
SAML parameters (identical to the white-label SSO)
⚠️ Once enabled :
→ any user with an address in the domain will have to log in via SSO.
6.2 New login workflow
To enable this hybrid system (classic login + SSO), Eventmaker has modified its flow:
Step 1 => The user enters their email.
Step 2 => Eventmaker analyzes:
Email belongs to an Enterprise SSO? → redirect to the SAML provider.
Otherwise → standard Eventmaker login.
⚠️ Even with Enterprise SSO :
The user must be invited to Eventmaker.
The invitation email must match the SSO email.