A signed-in bot is a Google Meet bot that logs into a real Google Workspace account on your domain before it joins.
It shows up as a named participant with an avatar, not an anonymous guest.
When that account is on the calendar invite it usually joins without knocking.
That depends on the meeting's access setting.
Why it exists
Two Google Meet settings decide how a bot gets in.
A signed-in meeting bot fits both settings.
How it is set up
Four steps, all of them one-time except the last.
The name and avatar shown in the meeting come from the Google account itself.
The Google Meet page has the steps.
How many logins to register
Google allows one account a set number of sessions at a time.
So plan for roughly one login per 20 concurrent Meet sessions.
MeetStream rotates across the logins you register.
Frequently asked questions
Does a signed-in bot skip the lobby?
When the account is on the calendar invite, yes. Otherwise it still joins as a named participant and asks to be admitted.
Do I need Google Workspace?
Yes, a Workspace account on a custom domain with Admin console access.
Can I use it on Zoom or Teams?
It is a Google Meet feature. Zoom uses OBF or ZAK, and Teams admission follows the tenant lobby policy.
How many logins do I need?
About one per 20 concurrent Meet sessions.
Put the vocabulary to work
One API to join, record, stream and transcribe meetings across Zoom, Google Meet and Microsoft Teams.