Google Meet link on the calendar: what guests see before joining

The event is on the calendar, the Google Meet link is in it, and the invitation went out. Two minutes before the start someone messages to say they are stuck on a screen asking to be let in. Someone else reports that the link in the forwarded email is not the link in the calendar any more. Neither of these is a bug, and neither of them is random.

A Meet link sitting on a calendar event is not a door that anyone can walk through. It is a reference to a meeting whose access rules live in three places at once: the guest list on the event, the account type of whoever created it, and the host controls attached to that specific meeting. Most of the confusion around Meet links on the calendar comes from changing one of those three and expecting the other two to follow.

The link is not the meeting

Google documents five starting points for a Meet link: Meet itself, Gmail, Google Calendar, Google Chat on mobile, and another scheduling system. They do not produce the same thing.

A link created in Meet and pasted into the notes of a calendar event is plain text. The event has no idea it is a meeting. Nothing on that event affects who can get in, because the guest list and the meeting are unconnected.

A link added through Add Google Meet video conferencing while the event is being created is attached to the event. From then on, the guest list on that event is part of the access decision, and the Join with Google Meet button appears for the people who were invited.

The practical test is what the event looks like when a guest opens it. If there is a real join button rather than a URL in the description, the link is attached. If it is a URL in the description, the meeting is effectively open to whoever holds that string, subject only to the host controls and the account type of the creator.

This matters more than it sounds, because copying a link out of one event and pasting it into another is a common shortcut. The copy carries no guest list with it. Two events now point at one meeting, and the access rules that apply are the ones from the original.

What a guest actually sees, in three cases

The screen a guest lands on depends almost entirely on whether they are on the event and whether they are signed in.

Guest situation	What happens
On the invite, signed in to Google	Joins directly from the event or the link
Not on the invite, holding a forwarded link	Has to request to join and wait to be admitted
Not signed in to any Google Account	Has to request to join

Google is explicit that guests can forward the meeting link to other people, and that if an uninvited person tries to join, a participant from the organization has to accept their request first. For meetings organized by a personal Google Account, the rule is tighter: only the meeting creator can admit those participants.

That single sentence explains a large share of real world Meet failures. A meeting set up from a personal Gmail address, where the person who created the event is not the person who shows up first, has no one who can let anybody in. The room fills with people staring at a request screen while the creator is on a train.

The fix is not a setting. It is making sure the account that creates the event is the account that will be present at the start, or adding the people who need to get in to the guest list rather than relying on a forwarded link.

Host controls decide who has to knock

Access type is set per meeting, not per account, and Google names three levels.

Open lets anyone with the link in without knocking. Trusted lets anyone inside the host's organization in without knocking, plus anyone outside it who was invited through a Google Calendar event; everybody else knocks. Restricted admits only people invited through a Calendar event or pulled in from inside the meeting by a host, and is not available to consumer accounts.

Two details cause surprises. The first is that recurring meetings keep the settings of the first meeting, so a weekly call set to Restricted in January is still Restricted in June, including for the colleague who joined the team in March and was never added to the series. The second is that in an organization running Restricted access, in-domain users who are not on the event still have to knock. Being a coworker is not enough; being on the guest list is.

Access type is reachable in two places: from the event, next to Join with Google Meet, through video call options and then host controls, and from inside the meeting itself. Checking it once for a recurring meeting is worth more than checking it repeatedly for one-off calls, because the one-off call ends before the setting can do much damage.

The meeting code can change without anyone touching it

This is the failure that looks supernatural, and Google states the cause plainly. If Google Calendar events with Google Meet codes are created in Apple Calendar or other calendar apps, a new meeting code might be generated automatically to protect the privacy and security of the meeting, and an email notification goes out when it happens.

So the sequence is: an event with a Meet link gets created or edited through a calendar client that writes to Google Calendar without handling the conference data properly, Google replaces the code, the invitation everyone already has points at the old one, and nobody reads the notification email until afterwards.

Google's own guidance is to manage meeting links from Google Calendar, either at calendar.google.com or in its mobile apps. Anything else needs to be checked rather than assumed. A desktop calendar that issues the Meet link itself as part of creating the event, rather than pasting a string into a field, does not run into this, because the conference data is created the way Google expects. The difference is invisible until the day it is not, which is why it is worth confirming once with a test event and its guest list rather than finding out during a client call. The way a calendar app handles this is part of what Features means in practice.

Google also documents that meeting codes expire, and keeps a separate page on when, which is worth reading if the habit is to create a meeting well in advance and reuse the link. Long-dormant links are a category of their own.

Dial-in exists, but not for everyone

The phone number in the invitation is often treated as the universal fallback. It is not universal.

Dial-in works only when the meeting is organized by a Google Workspace user, and the number appears only when an administrator has turned the feature on. From a guest's side the number is either there or it is not, and no amount of retrying changes that.

The timing rules are specific. Callers can dial in from fifteen minutes before the meeting starts until it ends, and someone already in the meeting can let them in earlier. Anyone who calls in counts toward the participant limit. If the caller is in the organizer's directory their name shows; if not, they appear as a private caller, which is a reason to verify who is on the line rather than assuming.

All Workspace editions include a US phone number, and international numbers in video meetings are limited to certain editions, with more becoming available when an organization turns on global dialing. For an international guest list, checking which number the invitation actually carries is worth doing before the meeting rather than during it.

One more edge case: Google Workspace Essentials users cannot schedule a meeting in Google Calendar at all. If the Add Google Meet video conferencing option is simply absent, the account type is the first thing to check, ahead of any setting.

Sometimes the block is on the guest's side

Every setting discussed so far belongs to the host. There is a second set of rules that belongs to the guest, and it is invisible from the organizer's screen.

Google describes which meetings an account is allowed to join at all, and it varies by account type. A personal account, a Google One subscriber or a Workspace Individual subscriber can join any meeting organized by another account of those kinds, and only some meetings organized by other Google Workspace users, because certain Workspace administrators restrict access to their meetings. A Workspace account can, by default, join meetings organized by personal accounts, Google One, Workspace and Workspace Individual users, but an administrator can narrow that to meetings organized inside the organization only, or to meetings organized by Workspace users only. Education accounts are narrower again by default, and the administrator can either restrict joining to meetings organized within the school or open it up to anyone.

The consequence is worth stating plainly: a guest can be on the invite, signed in, and still be refused, because their own organization decided which outside meetings its people may join. No change on the host side will help.

When a guest cannot get in and everything on the event looks correct, the next question is which account they are using. Asking them to try with a personal account, or asking their administrator, resolves it faster than editing the event again.

What to fix on your own side

Most of the above is about guests. The host side has one recurring problem, which is not knowing that someone is waiting.

Google notes that a chime sounds as the first five participants join, and after that new arrivals produce a silent notification. In a meeting of any size, a request to be admitted is easy to miss entirely, especially while presenting.

Two habits remove most of the risk. The first is to put the people who must attend on the guest list rather than sending them a link, so the knock never happens. The second is to keep the join surface in front of you rather than in a browser tab: a calendar that recognizes the Meet link on an event and puts a join button on it means the meeting is one click from the day view, and the same applies to Zoom, Teams and Webex links that arrive from outside. The Guide covers where that button appears and what it does with links that came in as plain text.

It is also worth deciding, once, which account owns the meetings. Mixing a personal account and a work account across a recurring series is how the admit-nobody situation gets built by accident.

What to change first

Open the next recurring meeting on the calendar, check its access type, and confirm that everyone who needs to be in the room is on the guest list rather than holding a forwarded link. Then check that whatever creates the event is issuing the Meet link itself instead of writing a URL into a field, which is the difference between a link that survives an edit and one that quietly gets replaced. Caltimate issues Zoom and Meet links as part of creating the event and puts a one-click join button on anything it recognizes.