Skip to content
All posts
Guides

Meeting Transcription Tools With SSO and Security: What to Check

Every meeting transcription tool for companies lists SSO. What separates them is whether your admin can set it up alone, enforce it, remove leavers automatically and see every change. Here is the checklist IT works through, with Kalima's answers and the things it does not do.

Kalima Team5 min read

Short answer: look for single sign-on through SAML 2.0 or OpenID Connect that your admin can set up without the vendor, the option to enforce it, SCIM so that people removed in your identity provider lose access, two-factor sign-in for everyone else, an IP allowlist, and an audit log you can export or stream. Kalima Enterprise has all of them: self-service SAML 2.0 and OIDC with setup guides for Microsoft Entra ID, Okta, Google Workspace and JumpCloud, enforcement with an emergency access for owners, SCIM 2.0, IP allowlists and audit streaming to an HTTPS endpoint or Splunk. On top of sign-in, check where recordings are processed and whether a bot joins your calls. Kalima's servers are in Germany, AI runs in EU data centres, and recording happens on the user's own computer, so no bot joins.

The checklist

QuestionWhy it mattersKalima
SAML 2.0 or OIDC?Your identity provider decides which one worksBoth
Self-service setup?Waiting for the vendor delays the rolloutYes, in the Kalima Console, with a required test sign-in before you turn it on
Can SSO be enforced?Otherwise people keep signing in with a passwordYes, for company accounts on your verified domains. Owners keep an emergency access with password and two-factor, and every use is logged and emailed to all owners
SCIM?Leavers must lose access without a ticketSCIM 2.0: removing someone in your identity provider suspends the account and signs them out everywhere. Groups become teams
Two-factor sign-in?For people outside SSO and for adminsAlways required for owners, admins and console roles, and can be required for all members. Passkeys count as a second factor in the browser
IP allowlist?Limits sign-in to company networksYes, for the console only or for the console and the app
Audit log?Who changed which setting, when, from whereEvery company plan has one that cannot be edited, exportable as CSV or JSON. Enterprise can stream it
Data location and AIWhere audio and transcripts are processedServers in Germany, AI processing in EU data centres, no AI training on your recordings

Limits worth knowing

  • No sign-in from an app tile. Users start at Kalima's sign-in page with "Continue with SSO". Sign-ins started from the identity provider's app launcher are not accepted.
  • Groups map to teams through SCIM, not through SSO.
  • No certifications. Kalima holds no SOC 2 or ISO 27001 certification.
  • Keys are managed by Kalima. There are no customer-managed keys.

What the admin does not see

Strong sign-in is half of security. The other half is what an administrator can do once signed in. In the Kalima Console, admins manage members, policies and sign-in, but they never see recording content or titles, and usage appears only by team, never per person. A member's private recordings stay private.

Which plan

SSO, SCIM, IP allowlists and audit streaming are part of Enterprise, which starts at 10 seats and is set up with our team. Team (2 to 25 seats) includes the console, two-factor rules, the audit log and company policies. Talk to us for Enterprise, or see pricing.

Try Kalima on your next call.

Live transcription and translation, no bot in the meeting. Free to start.

Start for free

Keep reading.