Anthropic adds Claude Whiteboards to Google Meet calls

Anthropic announced Claude Meetings on November 10, 2026, with a forthcoming Team and Enterprise feature that adds Claude to Google Meet calls to take notes and update documents while people talk. Separate Anthropic Help Center documentation describes the coming release’s live-whiteboard beta.

The announcement places Claude inside live workplace conversations. Anthropic’s stated design goal is to preserve context as work changes format. Meetings applies that approach during a call, where spoken requests can become structured material that a team continues using after the meeting ends.

Anthropic is presenting the result as a workflow that joins note-taking, diagramming and document production while preserving context. The workplace stakes are concrete: a spoken request can feed directly into material that the team can edit, organize and reuse.

What can the whiteboard do during a call?

Anthropic’s Help Center documentation calls the whiteboard feature a “live-whiteboard beta.” It labels Claude Meetings “coming-soon” as a whole. This distinction matters because the beta and availability limits apply specifically to live whiteboards, not every feature associated with Meetings.

The beta applies to Team and Enterprise plans. Google Meet is the only initially supported meeting service; Microsoft Teams and Zoom are unsupported at launch.

On Team and Enterprise plans, a user can start a live whiteboard from the meeting’s page in Claude. The user can also start one from the meeting event page beginning 30 minutes before the meeting and continuing until the meeting ends. Starting it through that event-page route adds Claude to the call.

Only people who can edit the meeting can start its whiteboard. Once the board has started, anyone with access to the meeting can open it. Starting rights and viewing rights therefore remain separate.

Participants can give Claude spoken requests, such as asking it to put a timeline on the board. Whiteboards accept spoken, typed and sketched input. Claude organizes that material with shapes, arrows and sections. It also groups related ideas, orders steps and connects dependencies. Everyone on the board can rearrange the content together while the call remains live.

The board remains an editable artifact, not a fixed summary. It behaves more like a shared work surface than a locked transcript. Users can ask Claude to regroup the material by theme, turn it into a timeline or suggest missing steps for review. Participants can also change the arrangement themselves as the discussion develops.

Every board is saved in the Artifacts tab. Claude can convert the finished board into a document or a slide deck. The saved board therefore gives a Google Meet discussion a path into later work, with the option to remain a visual planning artifact or change format.

Who controls access and sharing?

Administrative and commercial controls are explicit in the documentation:

• Default access. Whiteboards are on by default for Team plans.
• Enterprise activation. Enterprise organizations start with the feature disabled. An administrator must enable it under Organization settings > Artifacts.
• Sharing. Artifacts remain private until someone shares them. On Team and Enterprise plans, links stay inside the organization unless an Owner or Primary Owner enables external sharing.
• Usage and billing. Whiteboards count toward plan usage limits. Boards created during a Claude Meetings call follow Claude Meetings pricing.

These rules draw on controls already attached to meetings, artifacts and organizations. A participant does not need a separate whiteboard role to open a board, while activation and external distribution remain tied to organization roles.

Together, these settings put activation and external distribution in administrators’ hands. They also place whiteboard consumption inside Anthropic’s existing plan metering, so administrators must evaluate governance and consumption together during any rollout.

What data can Claude use?

Anthropic defines a narrow input boundary. Claude Whiteboards works from the contents of the board and does not use context from connected applications. That limit constrains the information Claude can bring into the exercise from other systems, even where those connectors are available.

Whiteboards are unavailable to organizations with HIPAA-ready configurations.

For organizations operating zero data retention for Claude Code, whiteboards remain available in chat and Cowork. That retention setting does not cover those boards, and whiteboards are unavailable within Claude Code itself.

These exclusions make the feature’s data posture conditional on organizational configuration. A connected application does not become an automatic source for a board, and a code-specific retention choice does not govern boards used in chat and Cowork.

How does Meetings fit the wider artifact system?

The Meetings announcement sits inside a broader artifact release. The same overview introduces Claude Sheets, Claude Whiteboards and Claude Data, alongside expanded interactive connectors. Anthropic presents these tools as ways to carry context between different kinds of work.

Anthropic describes its broader design as preserving “context as work changes format.” An idea can move from a whiteboard to a spreadsheet or dashboard without the user restating the details. Meetings is intended to bring that approach into the call, where discussion can become material the team continues using elsewhere.

The announcement therefore positions Meetings as a bridge between live discussion and Anthropic’s artifact system. Whiteboards provide the initial visual layer, while Sheets and Data extend the same context into other formats.

The practical sequence stays short. A participant requests a structure during the call, adjusts it with Claude and other participants, saves it in Artifacts and converts the finished work. Each stage keeps the board as the source, even when the output changes. Anthropic’s connected-app boundary means that continuity comes from Claude’s own artifact context rather than imported data during the exercise.

What does the launch mean for teams?

The launch is controlled rather than universal. Availability depends on plan, administrator activation, meeting platform, sharing role, usage metering, HIPAA-ready status and the retention configuration used for Claude Code. Those conditions will shape practical adoption alongside the feature’s ability to organize a discussion.

For organizations evaluating Claude Meetings, the documentation gives teams a defined route from a live request to a saved, convertible artifact. It also gives administrators explicit boundaries for enablement, external sharing, retention and use with connected applications. The result is a bounded first release: one meeting platform, two plan tiers and several organization-specific controls.

The next stage of Anthropic’s strategy will depend on whether teams can move a live discussion into the wider Sheets and Data workflow without separating the artifact from the controls that govern it. Until then, Claude Meetings remains a coming-soon product with a narrow, documented whiteboard beta.