Class starts at six. You're in the Meet, your slides are up, and the messages start. One student has been on 'Asking to join' for five minutes. Another got 'You can't join this video call'. A third says the link doesn't work. Two people made it in.
This is rarely a Meet outage. Who gets straight in, who has to knock and who gets turned away is decided by three things: the meeting's access setting, the Google account each student is signed in with, and the account you created the meeting from. Sort those out and the same link works for everyone.
A OneSol class page on Pro ($9/month) takes bookings and payments into your own Stripe or PayPal, and emails your Meet link only to students whose spot is confirmed.Make your class page →The quick answer: match what the student sees to the cause
Ask each student exactly what is on their screen. The wording points to a different fix.
- Stuck on 'Asking to join': they have to knock, and nobody allowed to admit them is answering. On a meeting made from a personal Google account, that is only you.
- 'You can't join this video call': Meet turned them away instead of letting them knock, usually because of the account they are using or a host setting.
- The call ended for everyone at the hour, or they see 'Your meeting is full': the limits on meetings hosted from a personal Google account.
- The link leads nowhere: an expired meeting code, a nickname used outside its organization, or a code typed wrong.
Stuck on 'Asking to join': nobody is there to let them in
Anyone who isn't allowed straight in has to knock, and waits on 'Asking to join' until someone accepts. Google's help describes three meeting access types, set per meeting. 'Open': anyone with a meeting link joins, and no one has to knock. 'Trusted': people in the host's organization, and guests invited through a Google Calendar event, join without knocking; everybody else knocks. 'Restricted': only Calendar invitees and people a host invites from inside the meeting skip the knock.
On personal accounts, Google says new meetings are 'Trusted' by default and 'Restricted' isn't available. Meetings created through Google Classroom start as 'Restricted'.
So if you teach from a free Gmail account, any student who isn't a guest on the Calendar event knocks every time. And Google says that for meetings organized by a personal Google account, only the meeting creator can admit them, and the organizer should stay in the meeting to approve requests. If an assistant runs today's class from a meeting you created, or you drop out for a minute, nobody can let anyone in.
Waiting before you arrive? With 'Host must join before anyone else' turned on, or on a Classroom meeting, nobody gets in until you do. And Google says that after a meeting has ended, the link still opens, but no one can join until the host restarts the meeting.
School and work (Google Workspace) accounts have more room. With 'Host management' on, hosts and co-hosts can accept knocks; with it off, any participant from inside the organization can. Google's co-host page lists Workspace editions, including all education editions, not personal accounts. The fixes:
- Admit them now: when the request appears, click 'Admit'. With several people waiting, click 'View all', then 'Admit all'.
- Let anyone with the link straight in: at the bottom right of the meeting, click 'Host controls', scroll to 'Meeting access', choose 'Open' and click 'Save'. The trade-off is that anyone the link is forwarded to gets in too.
- Let only your students skip the knock: add each student as a guest on the Google Calendar event, using the address they actually sign in with.
- Set it before class: open the event in Google Calendar, click 'Video call options', then 'Host controls', and scroll to 'Meeting access'.
- On a school or work account, share the job: turn on 'Host management', open the People panel, click the menu next to a colleague's name and choose 'Grant host controls'.
'You can't join this video call': the wrong account, or school and work rules
This message looks final, and waiting won't fix it. Google's help pages don't explain this exact wording, but they document the situations where Meet refuses someone outright instead of letting them knock. Ask the student which account they are signed in with, then work down this list.
- A school account joining a personal-account meeting. This is the big one for tutors. Google's Meet help says Google Workspace for Education users can, by default, join meetings organized by Google Workspace users, which leaves out meetings made from a personal Google account. Classroom's help says students on K-12 education accounts won't be allowed to join Meet calls created by personal Google accounts. The school's admin can change it to 'Join meetings organized by anyone'. Otherwise, host from an account the school accepts.
- A work account with rules. Workspace admins can limit their users to 'Only join meetings organized by someone in your organization'. Only that admin can change it.
- The wrong account. Calendar guests skip the knock only when they are signed in as the address you invited. Have them switch to that account, or open the link in a private window and sign in only with it.
- Not signed in. Google's own pages disagree on whether a signed-out guest who tries 'Ask to join' can be let in or is automatically denied, and Classroom's help says they can't join meetings organized by Google Workspace for Education users, except by phone. Tell students to sign in first.
- Denied twice. On education accounts, Google says a participant whose requests are denied twice can't ask to join that meeting again. The organizer can still invite them back manually.
- Removed and blocked. A blocked participant stays out of that meeting, and any concurrent meeting using the same code, until they are re-invited from within the meeting.
- Knocking switched off. If the host unticks 'Anyone with the meeting link can ask to join', Google says knocking is off for the entire meeting, so anyone not invited is turned away. Tick it again under 'Host controls' > 'Meeting access', or add the student as a guest.
The free-account limits that end or cap a class
If everyone got in and the class then stopped mid-sentence, look at the account the meeting was made from. These limits follow the host's account, not the students', so a one-to-one lesson is fine and a group class that runs past the hour is not. Google's Meet requirements page lists them for hosts who don't have a Google Meet subscription:
- On a computer, one-on-one meetings can run for up to 24 hours. Meetings with 3 or more participants run for up to 60 minutes.
- At 50 minutes, everyone receives a chime and a message that the meeting is about to end. To extend it, the host can upgrade their Google account. Otherwise the meeting ends at 60 minutes.
- Personal accounts can have a maximum of 100 participants in a meeting. When a meeting reaches its limit, people trying to join see 'Your meeting is full'. Google counts device connections, so two students sharing one laptop count once.
The link itself: old, a nickname, or typed wrong
If a student never even reaches the 'Ask to join' screen, look at the link or code they are using.
- An old link. Google says a code made in Google Calendar expires once it hasn't been used for 60 days and isn't associated with any future calendar event. Codes made from the meet.google.com homepage, Gmail, Google Chat or Google Classroom expire 365 days after last use. Send the link from this class's event, not last term's email.
- A nickname. Google says you can only use meeting nicknames with people in your organization, and codes behind a Google Workspace nickname expire as soon as everyone leaves the meeting. Give outside students the full link.
- Typed wrong. At meet.google.com, click 'Enter code', type the code from your invite, click 'Join', then 'Join now'. Or open the Calendar event and click 'Join with Google Meet'.
- A recurring class. Google says recurring meetings keep the same settings as the first meeting, so set access on the Calendar event rather than only inside one session.
Before your next class: a short checklist
Five minutes of setup saves the first ten minutes of every class.
- Create the meeting from an account your students can join. If they use K-12 school accounts, a meeting made from a personal Gmail account won't let them in by default.
- Add every student as a guest on the Google Calendar event, using the address they sign in with, so they skip the knock.
- Choose the access type in advance under 'Video call options' > 'Host controls' > 'Meeting access': 'Trusted' with invited guests, or 'Open' if a forwarded link letting anyone in is acceptable.
- Leave 'Anyone with the meeting link can ask to join' ticked unless you want uninvited people turned away.
- Join a few minutes early and stay in. On a personal account, only you can admit people who knock.
- On a school or work account, turn on 'Host management' and add a co-host, so someone else can admit late arrivals.
- Check length and size: on a personal account, group meetings stop at 60 minutes and cap at 100 participants.
- Tell students to sign in to the right Google account before clicking, and to message you if they're turned away rather than retrying.
If students pay for the class
If students pay for your class, a OneSol class page on Pro ($9/month, first month $1) takes the booking and payment into your own Stripe or PayPal, and emails your Meet link only to students whose spot is confirmed. OneSol doesn't run the call itself, and it doesn't sync with Google Calendar, so students who book this way aren't guests on your Meet event: admit them when they knock, or set the meeting to 'Open'.
