On Team plans, inviting Claude to your meetings is available by default. That 1 line in the launch post is the whole story for an office, because the tool now arrives before the rule. Claude Meetings went into beta on November 12, 2026, on Team and Enterprise plans, and it joins a Google Meet call as a visible participant that takes notes, answers questions in the call and starts building documents while your team is still talking. A firm that reads the feature list first and the settings second will hold its first AI-attended client call before anyone has decided who agreed to be transcribed.
The direct answer: Claude Meetings is live in beta on Team and Enterprise plans, on Google Meet only. On Team plans an admin can turn inviting off, and on Enterprise plans an admin turns it on. Claude stays out of calls with outside guests by default, and it saves a transcript, a summary and screen descriptions for each meeting, not audio. Set the guest rule, the notice line and the page owner before the first call, this week.
- What Claude does inside the call
- The 3 defaults that decide your risk
- What a Canadian office sets before the first call
What Claude does inside the call
Claude appears on the call as a participant and posts a notice in the call chat. Your team can ask it questions out loud or in chat, and it answers in writing by default. With a person’s permission it can use that person’s connected tools, and it asks the first time, with the yes carrying forward to later calls. During the call it builds the working record as you go: the notes, the action items, a document or a whiteboard your team edits live. After the call, the notes, the transcript and anything it built sit on a page for that meeting inside your account, open to the people from your organization who were on the invite.
The beta terms are plain. Notes and transcripts carry no separate charge during the beta, and the documents and other artifacts Claude makes in a call are free through February 10, 2027. An answer that uses 1 of your connected tools counts toward your plan usage. The feature sits beside the rest of the current Claude build-out for offices. Claude Sheets is simple on purpose. Claude Data is the real call covers the Sheets, Whiteboards and Data release from the same week, including the admin decisions that release asks for. Meetings asks for the same kind of decision, on a shorter clock, because a meeting happens on a schedule whether the rule is written or not.
The 3 defaults that decide your risk
The first default is the guest rule, and it is the strongest setting in the launch. Claude is set to stay out of a call when someone from outside your organization is invited, and to leave if an outside guest joins partway through. An admin can allow Claude on guest calls. On those calls Claude posts its notice in the chat and does not reply there, and what guests say still lands in the notes and the transcript. For a Canadian firm, the guest call is the client call, the vendor call and the sales call. The default protects exactly the calls where a transcript can do the most harm, and an admin who relaxes it for convenience has made a records decision for every client on the calendar.
The second default is the record itself. Claude saves a transcript, a summary and descriptions of what appeared on screen. It does not save audio. That record is a business document from the moment it exists, and it holds personal information about your staff and your guests. Canadian privacy law keeps your firm accountable for what a tool does with personal information on your behalf, a point this site made when the finance tools raised the same shape of question. Claude Personal Finance Canada is still US-only. Ban bank CSV pastes first set the pattern: the firm’s rule lands before the tool’s data does. Anthropic’s own setup guidance tells teams to make sure everyone on their calls is fine with being transcribed before Claude or auto-join is turned on. Treat that line as a work order, not a footnote.
The third default is who can turn the thing on. On Team plans the ability to invite Claude is on, and the admin’s job is to decide whether it stays on. On Enterprise plans the admin turns it on for all or part of the organization, which means the Enterprise rollout can be staged team by team. The beta also skips some organizations outright: those on zero data retention, HIPAA-ready setups or customer-managed encryption keys do not get the feature in this round. If your firm runs 1 of those setups, the decision is already made for this quarter, and the useful work is writing the rule now so it is ready when the beta widens.
What a Canadian office sets before the first call
Write 3 settings down before Claude attends anything. First, the guest rule: keep the default that holds Claude out of outside calls, and name the person who can approve an exception. Second, the notice line: the words your team says at the top of a call, and the line that goes into the calendar invite, so consent is a habit rather than a scramble. Third, the page owner: the person who reads the meeting pages each week, clears the ones that should not sit on a server, and owns the retention call. Give your AI agent an 8-line job description before access sets the same discipline for agents, a named owner and a written stop rule before access is granted. A meeting participant deserves the same page of writing.
Then run the first month on internal calls only. Let the team learn what the notes catch and what they miss, and let the owner build the clearing habit while the record holds nothing a client said. Your agent’s memory needs an editor, not a bigger limit makes the companion case for what these tools keep: a record with no editor grows into a liability at the speed of your calendar.
The recap fits on 1 line each. The tool is in beta, on Google Meet only, and on by default for Team plans. The guest default is the protection, the transcript is the record, and the admin switch is the decision. All 3 sit with your firm, not with the vendor.
Set the guest rule and the notice line before your next team call, and read Give your AI agent an 8-line job description before access for the access page that pairs with it.
