Your Company Blocked AI Notetakers. What You Can and Cannot Do Next
A blocked notetaker is either a switched-off transcription policy, a lobby that refused a bot, or a network that refuses the service itself. Only one of those is about something joining your call, and only one is a question you can answer without asking somebody first.
"The AI notetaker is blocked" describes three different situations that share a word. An administrator can switch off the meeting platform's own transcript. A lobby rule can refuse a notetaker bot at the door. A network or a managed laptop can refuse the transcription service itself. Only the first two are about something joining the call. This guide separates them, and is honest about which one recording on your own device changes and which one it does not.
Permission and possibility are not the same question
Whether you can produce a transcript and whether you may are separate questions, and the second one matters more. Your employer's acceptable-use policy, your client's NDA, the procurement terms behind a project and the law where the participants are sitting can each forbid transcribing a conversation when nothing stops you technically. A block you route around is still a policy you broke.
So ask. Your IT or security team can tell you what the block covers, the organiser can tell you whether they mind, and the client's contact can tell you whether their terms allow it. Then tell the people in the meeting that you are transcribing, every time, before you start. In Germany, § 201 StGB makes it a criminal offence, punishable by up to three years' imprisonment or a fine, to record the non-publicly spoken word of another person without authorisation, and to use or pass on such a recording. Rules elsewhere differ, sometimes by region. Agreement from everyone present is the path that does not require you to be a lawyer, and where real confidentiality is at stake, confirm it with your data protection officer or your counsel.
The three blocks, and which one you are hitting
| What is blocked | What it actually stops | Does capture on your own device change it? |
|---|---|---|
| Tenant transcription policy | The platform's own transcript, and separately its live captions | No, it was never about your device. It is not a recording ban either, just a switched-off feature |
| Lobby and bot admission rules | A third-party bot account joining as a participant | It does not apply, because nothing joins the call. It is not permission either, see below |
| Domain blocklist, network filter, device app control | The transcription service itself, on your work network or machine | No. This applies to Kalima like any other service. Ask IT |
Work out which one you have first. People routinely assume they are in case two when they are in case one, and treat case three as a bug.
Block one: the platform's transcript is switched off
In Microsoft Teams, transcription is a policy setting, not a permission that travels with you. Microsoft's admin documentation says transcription is both a per-organiser and a per-user setting: the organiser must have it turned on for the meeting to include a transcript, and the person who starts the transcript must have it turned on too (Microsoft Learn, "Manage transcription and captions for Teams meetings", page dated 6 July 2026, checked 22 September 2026). Administrators control it with the AllowTranscription setting, and live captions are a separate switch, which is why a meeting can offer captions and no transcript, or the reverse.
This is a feature being off, not a recording ban. Organisations usually switch it off because transcripts land in OneDrive and SharePoint and become discoverable records, which is a retention decision; whether you may record at all is a different policy, often in a different document. And none of it reaches your own machine, because the setting governs a Microsoft feature inside a Microsoft tenant.
Try the ordinary routes first: ask the organiser, use live captions if the captions policy allows them, or ask for the recording afterwards. Our guide to Teams transcription being greyed out walks through every cause, and a Teams transcript without recording the meeting covers the case where recording is what your organisation objects to.
Block two: the bot was refused at the door
This is the block that is new, and it is why "notetaker blocked" started appearing in searches this year.
Microsoft Teams ships an admin policy called "Manage external bots and their access to meetings". Microsoft's page names the target in its first line: "External meeting assistant tools (such as transcription or note-taking bots) are increasingly used in meetings", and lists recording or transcribing without participant awareness among the risks it addresses. Teams identifies these bots from "a combination of infrastructural and behavioral signals". A participant detected as a bot is "placed in the meeting lobby irrespective of the lobby configuration for the meeting", and the organiser has to admit it explicitly. The policy default is RequireApprovalWhenDetected, so detection is on unless an administrator turns it off (Microsoft Learn, "Manage external bots and their access to meetings", page dated 22 May 2026, updated 20 July 2026, checked 22 September 2026).
Google Meet changed how join requests are presented. Google's announcement describes a "safeguarded guest admit flow" that splits knocking participants into two queues, the second holding "requests from connections where the host is more likely to need a closer look before deciding to approve them", and states that "the default action for entries in this queue is to deny entry". Rollout began on 24 March 2026 for Rapid Release domains and 7 April 2026 for Scheduled Release domains (Google Workspace Updates, checked 22 September 2026). One point deserves precision: Google's announcement never uses the words "bot" or "notetaker". That link comes from the vendors, whose support pages tell customers that all bots, including their own, may be flagged as carrying potential risk and that a host has to admit them manually (Airspeed knowledge base, checked 22 September 2026).
Both rules govern the same thing: an account asking to enter the meeting. Capturing the audio your own computer is already playing is not that. Nothing asks to join, so there is nothing for a lobby to hold and no extra name in the participant list.
That describes the mechanism. It is not permission, and it is not the selling point. Whoever configured that lobby policy did not want the conversation processed by an outside service, and that intention does not evaporate because a different tool takes a different route. Treat the refused bot as a prompt to ask out loud: may I transcribe this meeting, and how?
Block three: the service itself is blocked
If your corporate network refuses the domain, or your managed laptop will not let you install software, nothing in this article helps. This block applies to Kalima exactly as it applies to Otter, Fireflies or Fathom, and pretending otherwise would be dishonest. The answer is a conversation with IT.
Go in with specifics rather than a request. IT needs to know what gets processed, where it goes, who can reach it and how it comes back out. The next section answers all four for Kalima, and the trust page collects the same facts in something easier to forward than a paragraph. Ask at the same time whether an approved tool already exists that nobody told you about.
If you are a guest in someone else's tenant
Consultants, agencies and freelancers hit a version of this that employees do not. As an external in the client's meeting you have no platform transcript to fall back on: Microsoft states flatly that "guests can't initiate convenience recordings", and that users in trusted organisations cannot start one either when they join a meeting in another organisation (Microsoft Learn, "Introduction to recording Microsoft Teams calls, meetings, and events", checked 22 September 2026). If the client's tenant also runs the bot-detection policy above, the notetaker your agency standardised on sits in the lobby until somebody admits it.
| Option | What you get | What it costs you |
|---|---|---|
| Ask the client to record natively and share the file | Their own transcript, under their governance, no new processor | Somebody there has to start it and remember to send it. The file sits in their storage under their retention rules, and you lose access when the engagement ends |
| Capture on your own device, with the client's agreement | A transcript you control, on any platform, including calls where you are a guest with no rights | You are processing the client's audio, which their NDA or procurement terms may forbid outright. It needs an explicit yes, ideally in writing, before the meeting |
| Take notes by hand | Always available, never a compliance question | It costs the attention the meeting needed, and misses the sentence that later turns out to matter |
Say the obvious thing plainly: a client's rules may bar both a bot and capture on your own device. Confidentiality clauses are often written about the information rather than the method, in which case processing their audio outside their systems is the part that is not allowed. Ask at the kickoff, not after the first disputed deliverable.
What Kalima actually does
Kalima records the audio your own machine is already playing, in the browser or in the desktop app for Windows, macOS and Linux. You start a session, choose your microphone, the meeting audio or both mixed into one transcript, and read along as it builds with speaker labels. It never connects to Zoom, Teams, Meet or Webex, which is why nothing joins the call and no extra participant appears. One laptop on a meeting room table works the same way.
Where the output goes: your own account, over encrypted connections, stored in the EU, never used to train models. Who can read it: you, until you decide otherwise, because sharing is off by default and every share link is revocable. What you can take away: exports as PDF, SRT, VTT, JSON or plain text, plus self-service data export and account deletion. Capturing meeting audio is included on every plan, including the free one, and the pricing page has the current limits.
None of that makes Kalima permitted where a bot is not. It is a different mechanism, not an exemption from your employer's policy, your client's contract or the law. What it does is make the honest version workable: ask, get a yes, say at the start of the call that you are transcribing, and still end up with a usable record.
Frequently asked questions
Is this allowed if my company blocked AI notetakers?
Not by default, and you should ask rather than assume. If notetakers were blocked because third-party services have to pass a security review, using a different unreviewed service breaks the same rule, whatever its architecture. If the block was aimed at bots in calls with client data, the concern was where the audio ends up, which applies here too. Ask your IT or security team and get the answer in writing.
My client's IT refused the notetaker bot. Can I record on my own device instead?
Only if the client agrees. The refused bot tells you their organisation has a position on outside tools processing their meetings, so treat it as a prompt to ask rather than a gap to route around. Ask your contact directly, say where the audio is stored and who can read the transcript, and note the answer somewhere findable.
Does switching off transcription in Teams also ban recording?
No. It turns off one Microsoft feature, often for storage and discoverability reasons rather than as a recording ban. Whether you may record is a separate policy, usually in a different document, so do not read the greyed-out button as either a yes or a no.
Will the organiser be notified that I am transcribing on my own device?
No. Kalima does not connect to the meeting platform, so there is no participant to display and no event for it to report. That is precisely why you say it yourself at the start of the call. Announcing it is the point, not a formality.
Related
- Why no bot joins your meeting: how capture on your own device works.
- Teams transcription greyed out or not available: every cause of the switched-off transcript.
- A Teams transcript without recording the meeting: when recording is the objection.
- What to say before you record: consent wording in English and German.
- Trust and privacy at Kalima: the processing facts to forward to IT.
Try Kalima on your next call.
Live transcription and translation, no bot in the meeting. Free to start.
Keep reading.
Can you record a job interview? Consent, state law and the AI Act question nobody answers
Five vendor blogs answer this with a state list and a consent form. None of them mention that a voice recording can trigger a biometric statute, none cover an EU employer interviewing a US candidate or the reverse, and none say what happens to the recording after the decision is made.
The Google Meet Transcript Exists and You Still Cannot Open It
You were in the meeting, the transcript was made, and Drive still shows you a Request access screen. Meet ties the transcript to the Calendar invite, cuts off meetings with more than 200 invitees, and leaves external guests out entirely. Here is each rule, and why the file came out in the wrong language.
'99 % accurate' means nothing: how to read a transcription accuracy claim, and how to catch the errors that matter
Every transcription vendor publishes an accuracy percentage, and none of them mean the same thing by it. This is how word error rate is calculated, what it weighs equally that you do not, and a 20-minute test you can run on your own recordings.