Claude Meetings Brings Claude Into Google Meet Calls in Beta - On by Default for Team Plans, Including Meetings With Outside Guests
Anthropic is rolling out Claude Meetings in beta on Team and Enterprise plans, letting teams add Claude to Google Meet calls as a participant that takes notes and builds documents during the call. On Team plans, both the feature and joining meetings with outside guests are enabled by default; on Enterprise plans it is off by default. During the beta it is unavailable to organizations using ZDR or CMEK, among others.
Anthropic has begun rolling out Claude Meetings in beta. The feature lets a team bring Claude into Google Meet as a visible attendee, where it listens to the discussion, writes notes, answers questions, and produces documents and whiteboards while the call is still going1. Team and Enterprise plans get it, through both Claude and the Claude Desktop app2. According to TechCrunch, the announcement came on November 10, alongside Claude Whiteboards and Claude Sheets3.
Before looking at what Claude does in a call, it is worth checking how the defaults differ by plan. On Team plans, the feature is enabled from the start, and Claude can also enter meetings that include people from outside the organization. On Enterprise plans, neither is available until an owner enables them2. The rest of this article focuses on what the organization deploying it needs to decide.
Opposite Defaults on Team and Enterprise
According to the Help Center, owners (and Primary Owners) control three items under “Organization settings > Products > Claude Meetings (beta)“2.
| Setting | Options | Team default | Enterprise default |
|---|---|---|---|
| Claude Meetings | Off / on for roles that include Meetings / on for everyone | On for everyone | Off |
| Meetings with external guests | Internal meetings only / allowed | Allowed | Internal meetings only |
| Members’ connectors in meetings | Whether Claude can use each member’s connected tools during a meeting | (No default stated) | (No default stated) |
On Enterprise plans, enabling it for only part of the organization is done through custom roles2. A Team organization that does not want the feature usable before employees have been told about it needs an owner to open this screen first and set a policy.
During the beta, it is unavailable to certain organizations, such as those that use zero data retention (ZDR), are set up for HIPAA, or manage their own encryption keys (CMEK)1.
How Claude Behaves When Outside Guests Are Present
When outside guests are not allowed, Claude does not join a meeting to which someone from outside the organization has been invited, and it leaves if an outside person joins midway. Another company’s notetaker bot joining midway also counts as an outside participant for this purpose2.
Where guests from outside are permitted, Claude remains in the call and continues to listen and take notes. It announces itself in the Meet chat yet does not respond to anything there. What guests say goes into the notes and transcript. The documents and whiteboards being built, along with the chat with Claude, live on a “meeting page” inside the organization; guests have no access to either the page or the follow-up email2. Separately from the owner’s setting, each member also has a personal setting for meetings with external guests.
To bring Claude in, a user connects Google Calendar from the Meetings screen in Claude, picks a meeting, and clicks “Add Claude.” The calendar connection requires an owner to have enabled Google Calendar for the organization. Users can also have Claude join all of their meetings automatically, or all except one-on-ones, but owners cannot configure auto-join on other members’ behalf2. If the host declines to admit Claude, it does not return to that meeting unless someone adds it again. Claude can remain in a single meeting for up to eight hours.
Anthropic asks users to confirm that everyone on the call agrees to transcription before adding Claude or turning on auto-join1. Claude is listed among the attendees and announces itself in the Meet chat, but getting everyone’s agreement is still up to the user.
Permissions During the Call, and Who Sees the Chat
During a call, people can address Claude by name out loud or type a message to it in Meet. Unless configured otherwise, its replies are written into that same chat2. A request such as “Claude, make a doc” produces a document or whiteboard on the spot and attaches it to the meeting page.
Claude can also use tools that members have connected, for example to send a Slack message. In that case, it uses a person’s connected tools only with that person’s permission. Permission is requested the first time and then stays in effect. For spoken requests, Claude will for now confirm who is speaking every time2.
The place an answer appears matters. Every participant can read what Claude writes in Meet’s chat, while the chat on the meeting page is limited to the organization2. If Claude answers in the Meet chat with, say, internal figures pulled from a connected tool, everyone in the call can see them.
What Is Stored, and What It Costs
Claude stores a transcript, a summary, and descriptions of the screen; it does not store audio2. Once the call ends, its meeting page collects the notes, which contain a summary and action items, together with the transcript and any artifacts; invited members from the organization are emailed a link to it. Those invitees can revise Claude’s output, and the page itself can be shared further within the organization. In an ordinary chat, users can also question Claude about earlier meetings they are permitted to see. Anthropic says it is working with partners including Gong, Granola, Fireflies.ai, and Otter so that meeting transcripts can be sent to existing tools1.
On pricing, Anthropic’s article says that during the beta, Team and Enterprise customers pay nothing for notes and transcripts, nor for answers during a call unless they use a connected tool. Answers that use a connected tool count toward the plan’s usage. Documents, whiteboards, and other artifacts produced in a call carry no charge until February 10, 20271.
What Organizations Should Decide First
In October, Anthropic released Claude for Google Workspace in beta, which brings Claude into Google Docs, Sheets, and Slides, and on November 5 it added a set of administrative features such as a security center and centralized management to Claude Enterprise. Meetings is a feature that places Claude inside meetings, where people from outside the organization may also be present.
From an administrator’s point of view, three points appear worth checking.
- Whether the organization is on a Team plan: On Team plans, the feature and joining meetings with outside guests are both enabled by default. Organizations whose internal rules put conditions on transcribing meetings should review the settings before rollout
- How connectors are handled: Owners have a separate control over Claude’s use of members’ connectors in meetings. Because anything from a connected tool that lands in the Meet chat can be read by all attendees, organizations that allow outside guests may want to decide this item at the same time
- Where the data lives: Transcripts and summaries remain on Claude’s meeting page and can be shared within the organization. When handing work conversations to an AI service, it is necessary to know what is kept and where
For now, only Google Meet is supported, and other platforms are described as coming soon1. Organizations that mainly use other meeting tools will have to wait for an announcement.
Sources
- Introducing Claude Meetings - Anthropic official article (November 12, 2026)
- Use Claude Meetings - Claude Help Center
- Anthropic launches Claude Meetings to turn workplace discussions into plans and tasks - TechCrunch (November 10, 2026)
Was this article helpful?
Thank you!
Received. Thank you!