Signing in to Kula

Last updated: September 17, 2026

Kula offers four ways to sign in: email and password, Google, Microsoft, and your company's single sign-on. Which ones you see depends on what your admin has turned on.

Who can do this: Super Admin 

Where to find it: Your Kula address, https://<your-company>.kula.ai

Your sign-in options

The Sign-in options section displays all available authentication methods for your organization. Each method can be toggled on or off using the toggle switch on the right. Enabled methods will be available on the Kula login screen for all users in your organization.

Sign-in Method

Description

Setup required

Email & Password

Users sign in with their Kula-registered email address and password

No setup required

Google

Users sign in using their Google account credentials

No setup required

Microsoft

Users sign in using their Microsoft account credentials

No setup required

Single Sign-On (SSO)

Users sign in via your organization's identity provider (e.g., Okta, JumpCloud, custom SAML)

Configuration required

Note: Only Super Admins can enable or disable sign-in methods. Changes take effect immediately for all users in the organization.

Email & Password

The Email & Password method allows users to sign in to Kula using the email address and password they registered with. This is the default sign-in method and is enabled by default for all organizations.

How it works

  1. The user navigates to the Kula login page.

  2. They enter their registered email address and password.

  3. On successful authentication, they are signed in to Kula

Note: It is recommended to keep at least one sign-in method active at all times to avoid locking users out of the platform.

Google

The Google sign-in option allows users to authenticate using their Google account. When enabled, a Sign in with Google button appears on the Kula login screen. No additional configuration is required to enable basic Google login.

How it works

  1. The user clicks Sign in with Google on the Kula login page.

  2. They are redirected to Google's OAuth flow and sign in with their Google account.

  3. On successful authentication, they are signed in to Kula.

Microsoft

The Microsoft sign-in option allows users to authenticate using their Microsoft account. When enabled, a Sign in with Microsoft button appears on the Kula login screen. No additional configuration is required to enable basic Microsoft login.

How it works

  1. The user clicks Sign in with Microsoft on the Kula login page.

  2. They are redirected to Microsoft's OAuth flow and sign in with their Microsoft account.

  3. On successful authentication, they are signed in to Kula.

Single Sign-On (SSO)

Single Sign-On (SSO) allows your users to sign in to Kula using your organization's existing identity provider (IdP). This is the recommended approach for larger organizations that want centralized access control and a seamless login experience for their team.

Kula supports SAML 2.0-based SSO. Once configured, users are redirected to your IdP for authentication and returned to Kula on success.

Configured providers appear in a list under Single Sign-On (SSO), each with:

Control

What it does

Edit

Change the configuration

Delete

Remove the provider

Toggle

Switch that provider on or off

You can have several configurations and switch each independently

Adding an SSO Provider

To add an SSO configuration:

1.  Navigate to Settings → Organization → Security.

2.  Under Single Sign-On (SSO), click + Add SSO.

3.  Select your identity provider or choose Custom SAML to configure manually.

4.  Enter the required configuration details provided by your IdP (SSO URL, Entity ID, X.509 Certificate).

5.  Click Save and use the Test Connection button to validate the setup.

6.  Once validated, enable the toggle to activate SSO for your organization.

After enabling SSO, users will be redirected to your identity provider for login. You can allow both SSO and direct login simultaneously, or enforce SSO exclusively.

Change which methods your team can use

  1. Go to Settings → Organization → Security.

  2. Under Sign-in options, turn each method on or off.

Kula will not let you turn off the last enabled method — that toggle is disabled, with the note "You need at least one login option enabled". You cannot lock your whole team out by mistake.

Before you switch your team to SSO

  • Tell people before you turn off email and password, so nobody arrives at a login screen they do not recognise.

  • Test with one account first.

  • If you use Google Workspace, consider auto-provisioning so your Kula user list stays in step.

  • Remove SSO configurations you no longer use.

Good to know

  • You can't disable the last remaining sign-in method — the toggle for it is locked, with an explicit "You need at least one login option enabled" note, so you can't accidentally lock your whole organization out.

  • Only Super Admins can change sign-in methods, and changes apply immediately to every user in the organization — there's no staged rollout or per-user override.

  • SSO doesn't have to replace other methods — you can run SSO alongside email/password, Google, and Microsoft, or turn those off to enforce SSO exclusively.

  • Test an SSO configuration with one account before rolling it out — and remove old SSO configurations you're no longer using, rather than leaving them toggled off indefinitely.

FAQ

No confirmed customer questions found yet for signing in and SSO setup.

Need Help?

If you have questions or need assistance with setup, feel free to reach out at support@kula.ai or use the in-app chat for help.