logo
Retrospectives
Planning Poker
Standups
IceBreakers
Pricing
Dashboard

Posts

Single Sign-On (SSO) Setup Guide

Single Sign-On (SSO) Setup GuideSingle Sign-On (SSO) Setup Guide Single Sign-On lets your team sign in to Kollabe using your company's existing identity provider - like Okta, Azure AD, or Google Workspace. No more separate passwords to remember! SSO is an enterprise feature. Once it's set up for your organization, you'll have full control over authentication settings.

Why Use SSO?

🔐Centralized Access Control

Your IT team manages who has access from one place - your identity provider.

🛡️Enhanced Security

Leverage your existing security policies like multi-factor authentication and password requirements.

👋Easier Offboarding

When someone leaves, removing their IdP access immediately revokes their Kollabe access too.

✨Better User Experience

One less password for your team to remember!

Getting Started

Prerequisites

Before setting up SSO, make sure you have:
  • An enterprise subscription (SSO is an enterprise feature)
  • Admin access to your company's identity provider (Okta, Azure AD, Google Workspace, etc.)
  • Super Admin or higher role in your Kollabe organization

SSO Setup Process

Request SSO
Contact support@kollabe.com to request SSO for your organization.
Access WorkOS Dashboard
We'll send you an admin link to the WorkOS dashboard where you'll configure SSO.
Configure Your Identity Provider
In the WorkOS dashboard, set up your identity provider and add your email domains.
Automatic Sync
Your domains are automatically synced to Kollabe via webhooks. SSO settings will appear in your Organization Settings.
That's it! Your IT team handles the identity provider configuration directly in the WorkOS dashboard.

Understanding SSO Settings

Once SSO is configured, you'll find two main toggles in Organization Settings:

Enable SSO

Turning this on adds SSO as a login option for users with verified email domains. What happens when you enable SSO:
  • Users with verified email domains can use the "SSO Login" button
  • Meeting access is automatically restricted to verified domains only
  • Other login methods (Google, GitHub, Email) still work unless you also enable provider restrictions
This is a good first step - it lets you test SSO while keeping other login options available.

Enforce SSO

This is the strict mode. When enforced, SSO is the only way to authenticate. What happens when you enforce SSO:
  • All other login methods are blocked (Google, GitHub, Microsoft, Slack, Email)
  • Users trying other methods will see an error message indicating SSO is required
  • Only the "SSO Login" button works for your organization's domains

Domain Configuration

Domains are configured in the WorkOS dashboard and automatically synced to Kollabe. Any domains you set up in WorkOS will be available for SSO authentication.

How SSO Login Works

The login screen always shows an email input field with two options:
  • SSO Login - Authenticates via your company's identity provider
  • Send Code - Sends a one-time password to your email
If SSO isn't enabled for their domain, users will see a message letting them know. If SSO is enforced and they try to use another login method, they'll see an error explaining that SSO is required.

Best Practices

Before Enabling SSO

  1. Complete the WorkOS setup - Make sure your identity provider and domains are configured in the WorkOS dashboard
  2. Test with a non-admin first - Have a team member test the SSO login before enabling for everyone
  3. Communicate the change - Let your team know SSO is now available

Before Enforcing SSO

Admin email domain is configured in WorkOS

Admin can successfully authenticate via SSO (tested!)

SSO connection is working with your identity provider

Team has been notified of the change

You have support@kollabe.com contact info accessible

Troubleshooting

Your email domain hasn't been configured for SSO, or SSO isn't enabled for your organization. Contact your organization admin to verify the domain is set up in WorkOS.

Your organization has SSO enforced, and you tried to log in with Google, GitHub, or email. Use the "SSO Login" button instead.

There's an issue with the identity provider configuration. Contact your IT admin to check the IdP setup in the WorkOS dashboard.

Your identity provider rejected the authentication. Verify you have the correct access in your company's identity provider.

Contact support@kollabe.com immediately. We can help restore access through manual intervention.

Common Questions

Yes! Unless you also enable "Enforce SSO", other login methods continue to work alongside SSO.

Nothing changes for existing accounts. When SSO is enforced, those users simply need to switch to the "SSO Login" button. All their data is preserved.

SSO is domain-based. All users with emails from verified domains will use SSO, while users from other domains can use regular login methods (unless you enable domain restrictions).

Yes! You can configure multiple email domains in the WorkOS dashboard.

Super Admin or higher roles can manage SSO settings in Kollabe. Domain and IdP configuration is done in the WorkOS dashboard.

Okta, Azure AD, Google Workspace, OneLogin, and any SAML 2.0 or OIDC-compatible provider.

Getting Help

Need assistance with SSO setup or have questions?