Kalima for Enterprise
Kalima gives IT, security and the works council what they need before a company-wide rollout: single sign-on, automatic provisioning, an audit log, deletion rules, and a console that never shows what was said.
Your own admins set it all up in the Kalima Console. Servers are in Germany, AI processing runs in the EU, and your recordings never train AI.
A rollout gets approved once the questions have answers
Before a transcription tool reaches every desk, someone asks how people sign in, who can see what, how long recordings are kept and what admins can look at. Kalima answers each of these in the product, not in a slide deck.
Your people keep recording the way they do today, in the browser, the desktop app or the phone app. The rules come from the console.
What usually holds a rollout back
Rarely the technology. Usually questions nobody settled beforehand.
Accounts nobody manages
When people sign up on their own, leavers keep their access and nobody knows which accounts belong to the company.
Rules every team handles differently
One team shares public links, another records without a notice. Without central rules, every team decides for itself.
Open questions from the works council
Who sees which recordings, is usage tracked per person, how long is data kept? Without clear answers, the rollout stalls.
How a company rolls out Kalima
Most companies start with the Team trial and move to Enterprise once they need single sign-on and automatic provisioning.
Connect your identity provider
Verify your domain, connect any provider that speaks SAML 2.0 or OpenID Connect, run a test sign-in and turn SSO on. The console has guides for Microsoft Entra ID, Okta, Google Workspace and JumpCloud. Once it works, enforce it.
Create accounts automatically
With SCIM, an account appears when someone joins your directory and is suspended when they leave. Directory groups become teams in Kalima.
Set the rules once
Decide which AI features are on, whether public share links are allowed, which notice everyone sees before recording and after how many days recordings are deleted.
What IT and the works council can check
Every change in the console lands in an audit log that nobody can edit. Enterprise keeps it visible for 365 days and can stream it to your own systems.
Audit log and streaming
Who changed what, when and from where, exportable as CSV or JSON and streamed to your SIEM as it happens.
No content, no tracking per person
The console never shows what was said in a recording. Usage is shown by team, and only for groups of five or more.
Deletion rules and legal hold
Delete recordings, or only their audio, after 30 to 365 days. A legal hold stops deletion for chosen people or projects without showing or moving any recording.
What Enterprise includes
Team already brings the console, roles, rules, usage by team and a 90-day audit log. Enterprise adds what larger companies ask for.
Before you record
Kalima runs on your own device, so nobody in the meeting sees it. That is exactly why you should announce it: tell everyone before you start and ask for their consent. If you use Kalima at work, agree on it with your data protection officer and, where there is one, your works council first.
Questions from IT and purchasing
The questions that come up most often before a company-wide rollout.
Related use cases
Plan your rollout with us
Tell us how many people will use Kalima and which identity provider you run, and we set up Enterprise or a pilot with you. For a smaller team, Team can be booked right away by card or tried for 7 days.