What is single sign-on?

Single sign-on lets somebody use the identity their employer already gave them. Practically it means an attendee or an administrator signing in with their work account rather than creating another password.

In practice at an event

Two separate questions hide inside one word. Organizer SSO covers the administrators who run the event in the console, and is usually the one an IT department asks about. Attendee SSO covers the people using the app, and matters mainly for internal corporate events where every attendee is an employee.

For a public conference, attendee SSO is meaningless — attendees come from hundreds of organizations. For a sales kickoff or an all-hands, it can be the difference between an approved purchase and a rejected one.

What to look for

Ask which of the two a vendor offers, which protocol, and on which plan. SAML and OIDC are the common protocols, and SSO is frequently fenced behind an enterprise tier.

Ask what SSO replaces rather than supplements: some products offer it as an additional login route while still creating local passwords, which does not satisfy a reviewer who wanted local passwords eliminated.

If single sign-on is not available and your reviewer requires strong authentication, the fallback worth proposing is multi-factor authentication on organizer accounts plus a short list of who holds one. It does not satisfy a federation requirement, and it does answer the underlying concern.

Where event67 stands

event67 does not offer SAML or OIDC single sign-on. Owner and administrator accounts are email and password, with distinct roles for super-admins, org admins and per-event moderators, and every administrative action audit-logged. Attendees do not have passwords at all: they arrive through a claim link tied to their invitation.

If SSO is a hard requirement in your security review, score it as absent rather than partial.