Introduction
Students can add people to Google Meet during live classes without even the teacher needing to invite them or let them in. We have seen this issue repeatedly in K–12 schools, where uninvited participants can disrupt lessons.
They can invite people who are not supposed to be in the meeting and they will cause problems like interrupting lessons and taking attention away from classwork. Making teachers spend more time removing these participants instead of teaching. Schools need a way to restrict students from adding unauthorized participants.
Google Meet’s built-in Host Management controls depend on the meeting settings and participant roles. For schools, controlling who joins a meeting is different from controlling who can add people. This guide explains the existing Host Management controls and how Safe Doc’s BlockMeetAddPeople policy restricts the Add people option for student accounts.
Why Students Adding People to Google Meet Is a Problem for K-12 Schools
Students using Add people in Google Meet.
The problem often starts when a student uses the Add people option in Google Meet to invite someone who is not supposed to be in the meeting, without the teacher sending the invitation.
We have seen this issue come up among teachers and school IT administrators, especially when students add other people from the school domain. Even after teachers remove unwanted participants, those people will be invited back into the meeting.
How Unwanted Participants Disrupt Classes
When unwanted people enter a class meeting, they can:
- Distract students and interrupt discussions.
- Play inappropriate audio or share unwanted content.
- Disrupt the lesson by bringing more people who were not invited by the teacher.
Make it difficult for teachers to keep the class focused. Teachers lose teaching time while they identify and remove participants.
Why Removing Participants Is Not Enough
Removing someone does not prevent students from inviting them again through Add people. And the person will be able to return, forcing the teacher to deal with the same problem again.
This shows that simply removing someone will not solve the problem. Schools that want to prevent students sharing Google Meet with outsiders need a way to restrict students adding unauthorized participants across student accounts, rather than relying on each teacher to manage the issue during a meeting.
Why Google Controls Aren’t Enough for Schools
Google Meet has built-in tools for managing participants and meeting access. These can be useful, but they do not all control the same action.
The Meeting access settings focus on who can enter. They do not remove the ability for an existing participant to invite someone. This is why restricting meeting access alone will not solve the problem when students use the Add people option in Google Meet.
Removing someone stops the disruption for the moment, but it does not stop students from inviting them again. The same problem will happen again.
Host Management: What It Can and Cannot Do
Host Management lets the meeting host control certain actions that participants can take. When it is enabled, regular participants who are not hosts cannot add people, However the Meeting roles matter. Hosts and co-hosts have different permissions from regular participants, and the options available can depend on the meeting setup.
A meeting-level setting still depends on the meeting roles assigned to people in that meeting. If the school needs the same restriction to apply to student accounts across classes, relying to configure each meeting will not provide the consistency the school wants. If a student is made a co-host, they can change the Host Management settings or add people in the meeting.
Google Meet Host Management settings.
Restricted meeting access
Restricted meeting access helps control who can enter a meeting. The host can set the meeting to restricted. People who were not invited through Google Calendar or added by the host cannot enter directly and must request access.
Google Meet Restricted meeting access settings.
It is different from limiting what an existing participant can do once they are inside, this setting does not stop students who are already in the meeting from inviting others using Add people. Teachers also need to handle access requests when someone tries to join.
What should an effective solution include :
- Block the invite path, not just the entry path. It should prevent students sharing Google Meet with outsiders.
- Teachers and co-hosts should still be able to manage participants using their usual Meet controls.
- It should apply to the student organizational unit (OU) so it doesn't depend on teachers to configure meeting settings. .
- Students or other participants should not be able to change the restriction.
- Be easy to manage, Admins should be able to deploy and maintain the setting centrally.
Why Controlling Who Can Join Google Meet Is Different From Who Can Invite Others
So these are separate controls for meeting access and participant management. Understanding the difference matters for schools that want to control how students add people during an ongoing meeting.
Meeting Access and Participant Management Are Different Controls
Google Meet lets hosts choose who can join a meeting through the Open, Trusted, and Restricted access settings. But controlling who can enter a meeting is different from controlling who can add someone after the meeting has started.
For example, a teacher can restrict a class meeting, but a student who is allowed to join could still want to invite a friend who is not part of the class. The meeting's access setting determines who can enter, but it does not directly remove the Add people option for participants already inside.
The same question comes up when students have different roles in a meeting. With a Host management setting, hosts can use certain controls, including adding or removing people. This means schools also need to consider who is given co-host access when trying to prevent students from adding people to Google Meet.
Controlling Who Can Invite Others
The question is no longer just who can enter the meeting. It is whether students can use the Add people option to invite someone else while the meeting is ongoing.
For schools, this leaves separate requirements: controlling who can enter a class meeting and also controlling the additional participants after joining.
How Safe Doc to Prevent Students from Adding Participants In Google Meet
How Safe Doc Blocks the Add People Option
For schools that need to prevent students from adding people to Google Meet, Safe Doc provides a feature-level policy for controlling participant invitations and managing Google Meet adding people.
We designed Safe Doc’s BlockMeetAddPeople policy specifically to address this issue. When the policy is enabled, the policy removes the Add people option for users covered by the policy.
"The Add people option is removed Directly from the Google Meet interface Itself. Therefore the policy is different from a general Google Meet access restriction. It focuses specifically on the participant's ability to add people during the meeting."— Neeraj Nanvani, Development Director of Safe Doc at xFanatical
Apply the Policy to Student Accounts
Administrators can configure BlockMeetAddPeople centrally through Safe Doc and apply it to a specific organizational unit (OU). For example, a school can enable the policy for student accounts while keeping teacher accounts outside that OU so teachers can continue using the Add people option.
This allows administrators to target the restriction at student accounts rather than relying on each teacher to configure meeting settings individually. Students covered by the policy can no longer use that option to invite additional participants, this helps schools restrict students from adding unauthorized participants.
Adding people to a video meeting in Google Meet is disabled by Safe Doc
To be clear about what this policy is not: BlockMeetAddPeople does not block other ways of inviting people to Google Meet. Like to share Meet links, send Calendar invitations, or join through phone or dial-in options where available.
How to Prevent Students from Adding People to Google Meet: Step-by-Step
Prerequisites
- Admin access: A Google Workspace Admin with Chrome Management privilege or Super Admin in the Google Admin Console.
- Safe Doc deployment: Safe Doc must already be deployed to the student OU you want to configure.
If you have not deployed Safe Doc yet, apply for a free 30-day trial license key. The trial license and sample policy JSON file will be sent to you by email.
Next, sign in to the Google Admin Console and deploy xFanatical Safe Doc to the student organizational unit (OU) where you want to apply the restriction. You can refer to the guide, How to Deploy Safe Doc To Your Students’ Chrome Browsers, and use your trial license along with the sample JSON file to activate the extension.
Steps for Configuring Safe Doc Policy Settings
- Sign in to the Google Admin Console.
- Go to Devices > Chrome > Apps & Extensions > Users & browsers, navigate to your Safe Doc policy configuration for the relevant organizational unit (OU).
- Click the xFanatical Safe Doc app.
- In the right-hand panel, under Policy for extensions, add or edit your policy configuration JSON to include "BlockMeetAddPeople".
"BlockMeetAddPeople": {
"Value": true
}
When the policy value is set to true, Safe Doc removes the Add people option from Google Meet for users covered by the policy. - Save the policy configuration.
- Check Google Meet to confirm that the Add people option is removed.
Alt text: Google Admin Console navigation to Chrome Apps & extensions and Users & browsers.
Frequently Asked Questions
- Can students add people to a Google Meet?
Yes, Participants can be able to invite others using the Add people option in the meeting. They can also share the meeting link or send a Calendar invitation to others.
- How can schools restrict students from adding people to Google Meet?
Safe Doc’s BlockMeetAddPeople policy removes the Add people option for student accounts.
Administrators can apply the policy to the student OU while leaving the teacher OU unaffected, helping schools restrict students from adding unauthorized participants.
- What is Host Management in Google Meet, and does it hide Add people for students?
Host Management lets meeting hosts control certain participant actions. When it is enabled, regular participants who are not hosts cannot add participants. It depends on the meeting setup and participant roles.
- Does Restricted meeting access stop students from inviting people?
No. Restricted meeting access controls who can join a meeting. It does not directly remove the Add people option for existing participants. If students are inviting others from inside a meeting, You can remove the Add people option using BlockMeetAddPeople.
- Which invitation options does the policy restrict, and does it affect students and hosts differently?
The policy restricts the Add people option within Google Meet. You can apply it to specific organizational units (OUs), such as the student OU, while leaving the teacher OU unaffected. Other invitation methods, such as sharing a Meet link or inviting people through Google Calendar, are not controlled by this policy.
Conclusion
Students inviting unwanted people to Google Meet can disrupt classes and take teachers’ time away from teaching. Host Management can limit what regular participants do, while Restricted meeting access controls who can join. Choosing the right settings depends on the problem your school needs to address.
For schools that need to prevent students from adding people to Google Meet, Safe Doc’s BlockMeetAddPeople policy lets administrators restrict the Add people option centrally for student accounts while leaving the teacher OU unaffected.
Start a free trial, if you have not yet deployed Safe Doc.
xFanatical Safe Doc
