Skip to main content
Hub SSO signs in the people using your hub. It isn’t the admin portal login (see Logging in and account access).

Set up SSO on a hub

  1. Open your hub and go to Contacts.
  2. In the OAuth Single Sign On (SSO) panel, click Enable.
  3. Choose the Type: OAuth, Google or Facebook.
  4. Enter your provider’s details:
    • Google: Client ID and Client Secret.
    • Facebook: App ID and App Secret.
    • OAuth: Client ID, Client Secret, Issuer URL and Scopes. Click Auto Discover to fill in the authorize, token and user info URLs from your provider’s .well-known/openid-configuration.
    Hub SSO: the Add OAuth Single Sign On (SSO) window with the OAuth type selected and Issuer URL, Client ID, Client Secret and Scopes filled in
  5. In your provider, allow your hub URL as a web origin and <your hub URL>/auth/oauth/callback as the callback or redirect URL. The modal shows the exact values for your hub.
  6. Click Test OAuth connection, then Add.
Use Edit field mapping to choose which provider fields fill which Komo contact properties.
To change or remove SSO, use Edit or Delete in the same panel.

How it works

  • Card data capture forms show a Sign in button under the form header, above the fields. You can change its text and colours in the form editor.
  • Players can still fill in the form as a guest. The or continue as guest divider under the button can be turned off with Show Guest Divider on the form’s Styling tab. To require sign-in, use an Access Policy.
    Hub SSO: a card data capture form with the Sign in button above the fields and the or continue as guest divider
  • Signing in verifies the player’s email and saves their provider details to their contact, using your field mapping. Form fields are then pre-filled from the contact, and fields set to Hide field if the contact already has a value for it are hidden.
  • Once a player is signed in, the button no longer shows on the hub’s forms.
  • To also show a sign-in icon in the hub header, open Contacts → Form verification → Manage forms and emails → Sign In and turn on Show Sign In Button. With SSO on, it starts the SSO sign-in.

Gate content behind sign-in

Use an Access Policy with the Sso authentication type to show a hub, card or form only to people who’ve signed in.

Sign people in from your own site or app

If your site or app already signs people in, pass their identity (email or a JWT) through the Embed SDK instead. See Access Policies, Mobile App Integration and the developer docs.