Claude Meetings joins Google Meet as a visible participant

Claude can now join a Google Meet call as a visible participant, follow the conversation, and start work while the meeting is still going. Claude Meetings is in beta and is starting to roll out on Team and Enterprise plans in Claude and Claude Desktop. Google Meet is the only platform supported now. Support for other video platforms is described as coming soon.

On the call, people ask by saying "Claude" and then the question, or by typing in the Meet chat. By default Claude answers in writing. It can also build artifacts during the call, including docs, whiteboards, and slides, and the Help Center says all artifact types are supported. Each one is attached to the meeting page. Teammates on the invite can edit what Claude makes. In the launch example, a team planning a customer event says "Claude, start a doc for this plan." Claude writes up what the team has said so far, and people on the invite keep editing while the call continues. Asked what last year's event cost, Claude requests approval to look it up, posts the figure in the meeting chat, and compares it with the current plan. A timeline can go on a whiteboard beside the doc.

When Claude joins, it appears as a participant and posts a notice in the call's chat. Its tile is live and shows its current state. It saves a transcript, a summary, and screen descriptions. It does not save audio. After the call, the meeting page holds the notes, including a summary and any action items, the transcript, and everything built. People from the organization who were on the invite can see the notes, edit what Claude made, and share the page with others in the organization. They also get a recap email with a link. Someone with access can later ask Claude about those meetings in a regular chat, or add Claude to the next one from the Meetings calendar.

Consent, guests, and what is saved

Before anyone adds Claude or turns on auto-join, the launch post and the Help Center both say to make sure everyone on the call is okay with being transcribed. Anything Claude posts in the Meet chat is visible to everyone on the call. The chat on the Claude meeting page is internal, so outside guests cannot see it.

What Claude does with outsiders is a setting, and the two pages do not describe the default the same way. The launch post says Claude is set, by default, to stay out of calls when someone from outside the organization is invited, and to leave if an outsider joins partway through. An admin can allow calls with outside guests. The Help Center is more specific. On Team plans, Claude can join calls with outside guests by default, and an owner can turn that off. On Enterprise plans, an owner must allow it first, and the organization default is internal meetings only.

When outside guests are not allowed, Claude stays out if an outsider is invited and leaves if someone from outside joins mid-call, including another company's notetaker bot. When they are allowed, Claude listens and takes notes, posts its notice in chat, and does not reply there. What guests say is included in the notes and transcript. Guests do not get the meeting page or the recap email. Live docs, whiteboards, and the meeting-page chat stay on that internal page. Each person also has a personal setting for meetings with external guests.

Connected tools follow the person who asked. Claude uses that person's tools only with their permission. It asks the first time, and a yes applies going forward. For now, a spoken question makes Claude ask each time to confirm who is speaking. Approval requests appear in the Meet chat when possible. If Claude needs to confirm a Claude account, the request appears on the meeting page.

Who can turn it on, and what the beta includes

The beta is not available to some organizations, including those with zero data retention, a HIPAA-ready configuration, or customer-managed encryption keys.

On Team plans, Claude Meetings is on by default. The launch post says an admin can turn it off; the Help Center says an owner can. On Enterprise plans, an owner turns it on for everyone or for part of the organization, using custom roles for a partial rollout. Owners and Primary Owners manage the product, the external-guest policy, and whether Claude can use members' connectors during meetings. On Enterprise, a custom role with Owner access can open that settings page as well.

A member adds Claude from Meetings after an owner enables Google Calendar for the organization. Auto-join is personal: all meetings, or all meetings except one-on-ones. Owners cannot set it for someone else. Claude usually joins without asking. If it does ask, the host can let it in. A decline means Claude does not try that call again unless someone adds it. Claude can stay for up to eight hours and warns before it leaves.

During the beta, notes and transcripts are free on Team and Enterprise plans, and so are in-call answers that do not use a connected tool. An answer that uses a connected tool counts toward that person's usage. The Help Center says that usage can lead to charges for the organization. The launch post says docs, whiteboards, and other artifacts Claude makes in a call are free through February 10, 2027. The Help Center names docs and whiteboards for that date.

Claude is working with partners including Gong, Attention, Granola, Fireflies.ai, Otter, and Plaud so teams will soon be able to send a meeting transcript to tools they already use. That handoff is described as coming soon, not as part of this beta.

If the plan is eligible, read the Help Center article on using Claude Meetings before anyone enables auto-join. Confirm the organization is not in an excluded data configuration, decide whether external guests are allowed, and get a clear yes from everyone on the call that transcription is acceptable.

Sources

• Claude Meetings claude.com
• Use Claude Meetings support.claude.com