Single Sign-On (SSO) with Okta, Microsoft Entra ID and SAML

With Single Sign-On your team signs in to meetergo through your own identity provider. meetergo connects your provider for you; there is no SSO page in the dashboard that you configure yourself.

SSO is part of the Enterprise plan. It is not an add-on you can buy on Light, Suite or Premium, and it is not included in the legacy Teams plan (now Premium). Pricing is individual, so talk to sales or write to support@meetergo.com.

What is supported


Protocols	OpenID Connect (OIDC) and SAML 2.0
Providers	Okta, Microsoft Entra ID (Azure AD), Google Workspace, Infomaniak, or any provider that speaks OIDC or SAML 2.0
Where sign-in starts	On the meetergo login page (SP-initiated). There is no tile in your provider's app dashboard that logs users straight in.
User creation	Just-in-time: the meetergo account is created on the user's first successful SSO login. No invitation needed.
Removing users	Not automatic. Blocking someone in your identity provider stops them signing in, but their meetergo user and its paid seat remain until you delete them on the Users page.

Every new user created through SSO takes a paid seat, exactly like an invited user. See Managing users and seats.

What we need from you

Send us these details and we will create the connection:

Organization name
Email domain of your users, for example yourcompany.com
Identity provider (Okta, Microsoft Entra ID, Google Workspace, other) and whether you want OIDC or SAML 2.0
Primary contact for the setup

We then send you the redirect URI for your connection. It looks like this:

https://login.meetergo.com/realms/meetergo/broker/<your-connection>/endpoint

<your-connection> is the name we create for your organization, so wait for our message rather than guessing it.

Older instructions name https://auth.meetergo.com/oauth2/idpresponse as the redirect URI. That address belonged to our previous login platform and stopped working when we moved to our own EU identity platform in July 2026. If your provider still has it, add the new URI and remove the old one.

Example: creating the app in Okta (OIDC)

In your Okta Admin Console, go to Applications → Applications
Click Create App Integration
Select OIDC - OpenID Connect as the sign-in method
Choose Web Application as the application type
Configure:
- App integration name: meetergo
- Grant type: Authorization Code
- Sign-in redirect URIs: the URI we sent you
- Sign-out redirect URIs: https://my.meetergo.com/login (optional)
- Controlled access: assign the users or groups who should reach meetergo
Click Save
Send us the Client ID and Client Secret from the application details

Microsoft Entra ID works the same way: register an application, add the redirect URI as a Web platform, create a client secret, and send us the client ID, the client secret and your tenant ID. For SAML 2.0, send us your metadata URL (or the metadata XML) instead of a client secret.

We usually enable the connection within one business day and tell you when it is live.

How your team signs in

Go to my.meetergo.com/login
Click Continue with SSO
Enter the work email address
meetergo forwards the browser to your identity provider
After signing in there, the browser returns to the meetergo dashboard

Enterprise SSO connections are deliberately never shown as buttons on the login page. The email prompt behind Continue with SSO is the only way in, which is why your users will not find a button with your company name on it.

Attributes we read

meetergo	Claim / attribute
Email	`email`
First name	`given_name`
Last name	`family_name`

Email verification and 2FA

Users in an SSO organization are never asked to verify their email address. Your identity provider owns the address, so the verification banner and the mail gate do not apply to them.
meetergo's own two-factor authentication stays opt-in per user and cannot be enforced company-wide. Enforce MFA in your identity provider instead: it applies before the user ever reaches meetergo.

Troubleshooting

"Invalid email" after entering the work address

The address is not connected to an SSO connection. Check that:

the address uses the email domain you registered with us (a personal address or a second company domain will not match),
the user is spelling the address the way it exists in your directory,
the connection is already live on our side.

Someone whose address is on a different domain can still use Continue with SSO once their meetergo account exists, because we look the account up directly. New users have to be on the registered domain. Only one email domain is mapped per meetergo account, so tell us if you need to change it. If a colleague signed up with a personal address before SSO existed, they can move it as described in How to change your email address.

"You are doing that too much"

The lookup allows ten attempts per minute. Wait a minute and try again.

Redirect loop, or your provider rejects the redirect

The redirect URI in your provider has to match the one we sent you character for character, including the connection name at the end. Check the client ID and client secret as well.

Nobody can sign in while SSO is being changed

Users can fall back to Forgot password on the meetergo login page, set a password and sign in directly. Nothing is lost, and SSO takes over again as soon as the connection works.

Names or email addresses arrive empty

Make sure the profiles in your provider carry email, given_name and family_name, and that those claims are included in the token or assertion.

FAQ

Can we switch our existing meetergo accounts to SSO? Yes. We connect your provider to the accounts that already exist under your email domain, so bookings, meeting types and settings stay where they are. Write to support@meetergo.com with the details above.

Can people still sign in with a password or with Google/Microsoft? Yes. Those methods keep working for accounts that already use them; SSO is added alongside them.

Do you support SCIM or automatic directory sync? Accounts are created just in time on first login. There is no automatic removal when someone leaves your directory, so delete departing users in meetergo to free their seat. If you need full provisioning, raise it with us during the Enterprise conversation.

Can each team use its own identity provider? No. The connection is mapped to your email domain and applies to the whole meetergo account.