Single Sign-On (SSO)
Let your team sign in with your identity provider on the Enterprise plan.
Single Sign-On lets the people in your organization sign in to Kalima using your company's own identity provider, so they reach Kalima with the same login they already use for everything else. SSO is available on the Enterprise plan and is configured together with the Kalima team.
SSO is an Enterprise capability. On Free, Plus, Pro, and Team, members sign in with email and password or with Google. To enable SSO for your organization, talk to the Kalima team about an Enterprise plan.
Why use SSO
SSO gives your members one login everywhere: they sign in to Kalima with the same company identity they use for your other tools, so there is no separate Kalima password to remember. Onboarding is faster, because access to Kalima follows automatically when someone joins your company. Offboarding is cleaner, since removing a person from your identity provider removes their path into Kalima at the same time. And your IT or security team keeps control in one place, alongside your other corporate applications.
How it works
SSO connects Kalima to the identity provider your company already runs. Instead of maintaining a separate set of credentials in Kalima, your members authenticate through your provider, and access to your Kalima organization is governed by your central directory.
Start with Enterprise. SSO is part of the Enterprise plan, so the first step is to set up Enterprise for your organization with the Kalima team.
Configure SSO together. The Kalima team works with you to connect Kalima to your identity provider. There is nothing to wire up yourself in the app, because it is set up collaboratively as part of your Enterprise onboarding.
Members sign in through your provider. Once SSO is live, your people open Kalima and authenticate with your company identity, then land in your shared organization and teams.
SSO controls how people sign in. What they can see and do inside Kalima is still governed by your organization and team roles. Plan your member roles alongside your SSO rollout so access lines up with responsibilities from day one. See Members & Roles.
What SSO does and does not change
- Sign-in: Members authenticate through your identity provider instead of a personal Kalima password.
- Sessions: A normal signed-in session still lasts up to 7 days before re-authentication, the same as any other Kalima account.
- Roles and permissions: Unchanged. Organization, team, project, and session-share roles continue to control what each person can do. See Roles & Permissions.
- Billing and seats: Unchanged. Enterprise is billed per active seat; link-based session viewers never count as seats. See Billing & Seats.
- Your data and features: Unchanged. Transcription, AI, the Studio, sharing, and everything else work exactly as they do on any plan.
Who it is for
SSO suits larger organizations that already centralize app access through an identity provider and want Kalima to follow the same policy. It also fits security-conscious teams that need access granted and revoked centrally as people join and leave, and organizations rolling Kalima out to a large number of people across multiple teams.
Getting started
SSO is configured as part of your Enterprise plan, so the path to enabling it is to talk with the Kalima team. They will scope your needs, set up Enterprise, and configure SSO with you. Enterprise pricing is custom.
FAQ
SSO is part of the Enterprise plan. On Free, Plus, Pro, and Team, members sign in with email and password or with Google. To add SSO, move your organization to Enterprise by contacting the Kalima team.
No. SSO is set up together with the Kalima team as part of your Enterprise onboarding. There is no self-service SSO setup screen to work through on your own.
No. SSO only changes how people sign in. Inside Kalima, your organization, team, project, and session-share roles still decide what each person can do. See Roles & Permissions.
No. Enterprise is billed per active seat, and link-based session viewers still do not count as seats. SSO governs sign-in, not how you are billed. See Billing & Seats.
A signed-in session lasts up to 7 days before re-authentication is required, the same as a standard Kalima account.