Single sign-on lets your organization's identity provider (Okta, Azure AD, Google Workspace, or any SAML/OIDC-compliant provider) control sign-in to Meetbook, rather than members signing in with individual passwords or personal Google/Microsoft accounts.

Availability

SSO is an enterprise-tier feature — it isn't available on standard self-serve plans. Contact support or your account representative to discuss enabling it for your workspace — see How to contact support.

Setup, at a high level

Choose your protocol

SAML or OIDC, depending on what your identity provider supports and your IT team's preference.

Exchange configuration

Meetbook provides the metadata your identity provider needs (entity ID, ACS URL, or equivalent), and you provide Meetbook with your identity provider's metadata in return.

Test and roll out

Verify sign-in works for a test account before enforcing SSO workspace-wide, so you don't lock out existing members mid-rollout.

Enforcing SSO

Once verified, SSO can be made mandatory for the workspace — members are then required to sign in through your identity provider rather than any other method. Coordinate this rollout with your IT team, since it affects everyone's sign-in flow at once.

Setting up SSO