Skip to content
Verifycate
Start for free

Enterprise identity

Single sign-on for staff, faculty, and event teams

Connect Okta, Microsoft Entra ID, Google Workspace, or another identity provider with OpenID Connect (OAuth 2.0) or SAML 2.0. Enforce SSO for verified domains and keep MFA at the identity provider.

Staff should not need a separate Verifycate password. On Pro, members can sign in through the organisation's identity provider, which keeps MFA, sign-in policy, and account lifecycle in the system your IT team already governs. Verifycate keeps the workspace role, so access rules inside the product do not change.

How it works

Single Sign-On

  1. 01

    Connect your identity provider

    Add the provider through OpenID Connect discovery or SAML 2.0 metadata. Register the exact redirect URI or ACS URL shown in Settings. For OIDC, keep the client secret with the provider; for SAML, give the provider the SP metadata URL.

  2. 02

    Prove your email domains

    Add a DNS TXT record for each work-email domain. Verified domains let members find the right SSO route from their email address and let an admin require SSO for that domain.

  3. 03

    Choose how members join

    Existing members keep their current role. Optionally enable just-in-time provisioning so a first-time signer joins when an asserted directory group maps to a workspace role. Enforce SSO when you want email and Google sign-in refused for the domain.

Event examples

Where this workflow helps

  • A university requires faculty and staff to sign in through Microsoft Entra ID
  • A conference team uses its existing Okta account for organisers
  • A training provider enforces SSO for its work-email domain

For event organisers

See it in your event context

For universities

Universities and higher education

Issue verifiable certificates for courses, conferences, workshops, student activities, and microcredentials. Design a template, import a cohort, handle late requests and corrections, and give every student a public page they can keep.

See the event workflow

For event organisers

Conferences and events

Prepare and issue conference certificates by recipient group. Add event branding, sponsor details, QR verification, and public certificate pages.

See the event workflow

For training organisers

Training programmes and bootcamps

Prepare and issue certificates for bootcamps, cohort-based courses, and workplace training. Organise learner details, course information, and completion recognition in a batch.

See the event workflow

Common questions

Which SSO protocols does Verifycate support?
OpenID Connect (OAuth 2.0) and SAML 2.0. The workspace settings show the redirect URI or ACS URL and SP metadata to register with your identity provider.
Does Verifycate enforce multi-factor authentication?
Verifycate does not run its own MFA. With SSO, MFA and sign-in policy are enforced by your identity provider. Email one-time codes and Google sign-in do not add a second factor.
Can we require SSO for our domain?
Yes, on Pro. Verify a work-email domain with a DNS TXT record, then enable enforcement. Email and Google sign-in are refused for members at that domain.
What happens if our Pro plan lapses?
An existing SSO connection stays manageable so an admin can turn enforcement off instead of being locked out, and existing SSO sign-in is not interrupted. Creating a new connection or enabling new enforcement requires Pro.
Do certificate recipients need SSO?
No. SSO is for workspace members. Recipients open a certificate or form link without a Verifycate account; public verification is anonymous.

Try single sign-on with your event

Start with 300 free credits. No card required.

Start for free See pricing