Claude Meetings: Admin and Security Settings Explained
•
13
MIN READ
AI Summary by Fellow
Anthropic’s Claude Meetings beta puts Claude inside a Google Meet call as a visible participant that takes notes, answers questions, and builds documents while people talk. For a security or IT team, the first questions are rarely about what Claude can build. They are about what is switched on by default, who can change it, what happens when someone from outside the company joins, and whether the feature is even available under your current Claude data configuration.
This guide answers those questions setting by setting. It covers the three organization settings, per-user auto-join, external guest behavior, the difference between Team and Enterprise defaults, and the beta exclusion for organizations using zero data retention, HIPAA-ready configuration, or customer-managed encryption keys. Everything below reflects Anthropic’s Help Center article “Use Claude Meetings” as reviewed on November 16, 2026. Because the feature is in beta, confirm each setting in your own admin console before you sign off.
What is Claude Meetings?
Claude Meetings is a beta feature from Anthropic that adds Claude to a Google Meet call as a visible participant. Claude follows the conversation, takes notes, answers questions in the call chat, and creates artifacts such as docs, whiteboards, and slides during the meeting.
A few facts matter for a security review:
Plans: Team and Enterprise only, in Claude and Claude Desktop. The rollout is gradual, so not every eligible organization has it yet.
Platform: Google Meet only during the beta.
Disclosure: Claude joins as a visible participant, posts a notice in the call chat, and its tile shows its live state. Anything Claude posts in the Meet chat is visible to everyone on the call.
What is saved: a transcript, a summary with action items, and descriptions of shared screens. Claude does not save audio.
Who sees the output: organization members on the invite receive a recap email with a link to the meeting page, where they can view the notes and edit what Claude made. The meeting page can be shared with others inside the organization.
Session limits: Claude can stay in a call for up to eight hours and warns before it leaves.
The Help Center article does not list a meeting-specific retention period, so ask your Anthropic contact how meeting transcripts and summaries interact with your organization’s existing data retention settings.
Where are the Claude Meetings admin settings?
Claude Meetings admin settings live in Organization settings > Products > Claude Meetings (beta). Owners and Primary Owners can open this page. On Enterprise plans, a custom role with Owner access can open it as well.
There is one prerequisite outside this page: members connect Google Calendar inside Meetings to choose which call Claude joins, and an owner has to enable Google Calendar for the organization first. If Google Calendar is off at the org level, members cannot add Claude to calls even when the feature itself is on.
What are the three Claude Meetings organization settings?
Claude Meetings has three organization settings: one that turns the feature on or off, one that controls meetings with external guests, and one that controls whether Claude can use members’ connected tools during a call.
Setting | Options | Team default | Enterprise default |
|---|---|---|---|
Claude Meetings | Off, on for roles that include Meetings, or on for everyone | On for everyone | Off |
Meetings with external guests | Internal meetings only, or allowed | Allowed | Internal meetings only |
Members’ connectors in meetings | Whether Claude can use members’ connected tools in meetings | Not stated in the Help Center | Not stated in the Help Center |
Claude Meetings (the feature toggle)
This setting decides who can use Claude Meetings at all. On Team plans it starts on for everyone, and an owner can turn it off. On Enterprise plans it starts off, and an owner can turn it on for the whole organization or only for roles that include the Meetings capability.
That role option is the main lever for a staged rollout. An Enterprise security team can enable Meetings for a pilot group (for example, product or engineering) while keeping it off for deal teams, legal, or anyone who regularly handles sensitive client information.
Meetings with external guests
This setting decides whether Claude can be present on calls that include people outside your organization. “Internal meetings only” keeps Claude off those calls. “Allowed” lets Claude join them. The external guest section below explains exactly what each option does in practice.
Members’ connectors in meetings
This setting controls whether Claude can use the tools each member has connected to Claude (such as a CRM, a document store, or a project tracker) while it is in a meeting. When it is enabled, Claude can only use a participant’s connected tools with that person’s permission:
Claude asks the first time it needs a person’s connected tool, and a yes applies to future requests.
When someone asks by voice, Claude asks each time to confirm who is speaking.
Approval requests appear in the Meet chat where possible, or on the meeting page if Claude needs to confirm the user’s account.
Connector usage counts toward the user’s own usage and can create charges for the organization.
The Help Center does not state a default for this setting, so check its current value before rollout. For a security team, this is the setting that determines whether a live call can reach into other systems, which makes it as important to review as the external guest control.
How does Claude Meetings auto-join work?
Auto-join is a per-user setting, and owners cannot set it on anyone’s behalf. Each person turns it on under Settings > Capabilities > Meetings > Auto-join and chooses between all meetings or all meetings except one-on-ones.
What this means for an admin:
There is no org-wide auto-join policy. Your controls are upstream: whether the feature is on, for which roles, and whether external guest meetings are allowed. Within those limits, each person decides how often Claude joins their calls.
Claude usually joins without asking. If Google Meet does ask, the host can admit Claude. If the host declines, Claude does not retry that call unless someone adds it again, and the user sees that it was declined.
Consent is left to the user. Anthropic’s own guidance is to make sure everyone on a call is comfortable being transcribed before adding Claude or turning on auto-join. If your organization has a recording notice policy, auto-join is where it needs to be communicated, because no admin setting enforces it.
Members can pause Claude by asking it to stop listening or from the meeting page, and resume it from the meeting page. They can remove it by asking it to leave or by selecting “Remove Claude” on the meeting page.
What happens when an external guest is on a Claude Meetings call?
Claude’s behavior with external guests depends on whether the organization allows external guest meetings. When they are not allowed, Claude stays out of any call where an outside person is invited, and it leaves if an outside person joins partway through. That includes another company’s notetaker bot joining the call.
When external guest meetings are allowed, Claude stays on the call but behaves differently than it does in internal meetings:
It listens, takes notes, and posts its notice in the call chat.
It does not reply in the call chat.
Guest speech is included in the notes and the transcript.
Guests do not receive the meeting page or the recap email.
The meeting page chat is internal, so guests cannot see it.
There is also a per-person layer. Each user has their own “Meetings with external guests” setting, so an individual can be more restrictive than the organization.
How do Team and Enterprise defaults compare?
Team plans start open and Enterprise plans start closed. On Team, Claude Meetings is on for everyone and external guest meetings are allowed until an owner changes them. On Enterprise, the feature is off and external guest meetings are limited to internal calls until an owner opens them up.
Team plan | Enterprise plan | |
|---|---|---|
Feature on by default | Yes, for everyone | No |
Partial rollout by role | Not listed in the Help Center | Yes, through custom roles |
External guest meetings by default | Allowed | Internal meetings only |
Who manages settings | Owners and Primary Owners | Owners, Primary Owners, and custom roles with Owner access |
Auto-join | Each user decides | Each user decides |
The practical takeaway: an Enterprise owner has to make deliberate choices before anyone can use Claude Meetings, while a Team owner should review settings immediately, because members may already have access.
Which organizations can’t use Claude Meetings during the beta?
While Claude Meetings is in beta, it is not available to organizations with zero data retention (ZDR), a HIPAA-ready configuration, or customer-managed encryption keys (CMEK). Anthropic lists these as examples, so other configurations may be excluded too.
What each of these means in Anthropic’s own terms:
Zero data retention: customer data is not stored at rest after a response is returned, except where needed to comply with law or combat misuse. Anthropic applies ZDR per organization.
HIPAA-ready configuration: the setup that allows a Business Associate Agreement for eligible Anthropic services.
Customer-managed encryption keys: the organization encrypts its stored Claude data with its own keys instead of Anthropic-managed ones.
These are the configurations healthcare organizations, financial institutions, and other regulated firms typically choose on purpose. If your Claude organization uses any of them, Claude Meetings will not appear during the beta. Anthropic frames this as a beta limitation, not a permanent one, so watch the Help Center for changes.
How should a security team review Claude Meetings before rollout?
A Claude Meetings review comes down to six decisions, and most of them take minutes once you know where the settings are.
Check eligibility. Confirm your organization is on Team or Enterprise and does not use ZDR, a HIPAA-ready configuration, or CMEK.
Decide who gets it. On Enterprise, use custom roles to enable Meetings for a pilot group first. On Team, decide whether “on for everyone” is acceptable or whether to turn it off until the review is done.
Set the external guest policy. Choose between internal meetings only and allowed, and verify the actual value in the console rather than relying on documented defaults.
Review members’ connectors in meetings. Decide whether a live call should be able to reach members’ connected tools, and confirm the setting’s current value.
Confirm Google Calendar. Make sure the org-level Google Calendar setting matches your rollout plan, since Meetings depends on it.
Communicate auto-join expectations. Because users control auto-join, publish guidance on when to turn it on and how to make sure every participant is comfortable being transcribed.
How do Fellow's admin settings answer the same security questions?
Claude Meetings is built to turn an internal Google Meet conversation into working documents in real time. Many organizations also need a governed record of the meetings their compliance team is accountable for, across every platform they meet on. That second job is what Fellow is built for. Fellow is the most secure AI meeting assistant and notetaker for enterprise organizations and regulated industries like law firms, private equity, hedge funds, and investment banking, and it works alongside Claude rather than replacing it.
Your compliance team decides the policy, and Fellow applies it. Here is how Fellow's workspace settings map to the questions above:
Security question | Fellow setting |
|---|---|
Which meetings are captured, and how? | Admins choose which recording methods are available (a visible Note Taker, botless recording through the desktop app, Zoom Native Capture, or mobile) and set workspace auto-record and restriction policies by internal or external attendees, keywords, and attendee count. A restriction stops recording even if another rule would turn it on. |
How long is meeting content kept? | Configurable data retention with separate auto-delete periods for recordings, transcripts, and AI notes, a zero-day option for recordings and transcripts, and shorter retention for specific meetings through rules (Enterprise). |
How is consent captured? | Consent capture lets attendees accept or decline recording before an auto-recorded meeting (Enterprise), and recording disclosure emails go to attendees ahead of time. |
Who can see meeting content? | Access permissioning, admin toggles that allow or block downloads and copying, and password-protected meeting recaps for anyone outside the workspace. |
Can sensitive content be removed? | Transcript redaction permanently removes selected sections from the transcript and recording. |
Can compliance review meetings across the workspace? | The compliance portal supports workspace-wide search, review, flagging, and audit of recorded meetings, and the workspace audit log records activity for admins (Enterprise). |
How does meeting data reach other systems? | Fellow's Claude integration and MCP Server give Claude and other AI tools access only to meetings the user can already view, once an admin enables them. The Fellow API, 50+ native integrations, and the Global Relay integration cover CRMs, task tools, and regulated archives. |
Is meeting data used to train AI? | No. Fellow never trains AI models on your meeting data, and Fellow is SOC 2 Type II certified, GDPR compliant, and HIPAA compliant with a Business Associate Agreement. |
Fellow provides these as configuration options. It does not decide what your regulations require, and it does not replace your compliance program.
Conclusion
Claude Meetings gives admins a short list of controls: the feature toggle, the external guest policy, members’ connectors in meetings, and the Google Calendar prerequisite, with auto-join left to each user. Team plans start open, Enterprise plans start closed, and organizations using ZDR, HIPAA-ready configuration, or CMEK are excluded during the beta. If your firm also needs a governed record of every meeting on every platform, Fellow keeps that record under your policies before any AI assistant reads it, and you can start a Fellow workspace to see the controls for yourself.
Frequently asked questions
Record, transcribe and summarize every meeting with the only AI meeting assistant built with privacy and security in mind.






