A Google Meet refusal can come from an invitation mismatch, an access rule, or a previous moderation decision. Ask the guest for the exact message and intended account before changing the room. Repeatedly sending the same link does not correct all of these causes.
Match the guest to the invitation
Compare the meeting address with the current trusted invitation. Ask which Google Account the guest used, particularly when a personal and work account share a browser. Trusted and Restricted meetings can treat invited identities differently from uninvited ones. If knocking is disabled, someone outside the permitted group can be declined automatically rather than appearing for host approval.
Review policies and earlier decisions
The organizer’s organization can restrict who joins, and the guest’s administrator can restrict which meetings that account may enter. A host cannot necessarily override those policies. Check whether the guest was previously removed with Block selected. That blocks the current meeting and concurrent meetings using the same code. In Education meetings, two denied join requests also prevent further requests until the organizer manually invites the person back.
Choose the matching remedy
Use the intended invited account for an identity mismatch. For a legitimate blocked guest, an authorized person must manually re-invite them from inside the meeting. Escalate organization restrictions to the relevant administrator with the exact message, account type, and meeting context. Check host-first or waiting-room conditions when the guest is waiting rather than explicitly refused. After the correction, confirm that the guest appears in the main room and can hear the intended session. Preserve deliberate access restrictions while fixing the individual problem; a refusal is not by itself a reason to make the meeting open to everyone with the link.
References
- Join a meeting
- Add or remove people from a Google Meet meeting or call
- Tips to control meeting access and participation
Reviewed against the linked official product guidance on November 4, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.