# What is a signed-in bot?

> A signed-in bot is a Google Meet bot that logs into a real Google Workspace account on your domain before joining, so it appears as a named.

Source: https://meetstream.ai/glossary/signed-in-bot

*By Sidhdharth Sivasubramanian, Co-founder and CEO, MeetStream*

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.

- **Workspace account**: on your domain
- **SSO profile**: MeetStream sign-in
- **Bot signs in**: named, with an avatar
- **Invited**: skips the lobby

*A real account joins; invited accounts enter without a knock.*

## Why it exists

Two Google Meet settings decide how a bot gets in.

- **Guest bot**: An anonymous participant Someone in the call clicks Admit Under host management only hosts see the request Blocked when the call is limited to signed-in accounts
- **Signed-in bot**: A real Workspace account It is a real account on your domain It can be put on the calendar invite An invited participant walks straight in

*The same call, joined two ways.*

A signed-in [meeting bot](https://meetstream.ai/glossary/meeting-bot) fits both settings.

## How it is set up

Four steps, all of them one-time except the last.

- **1**: Step 1
- **SSO profile**: Legacy, pointing at MeetStream's URLs
- **2**: Step 2
- **Certificate**: With a domain-specific issuer
- **3**: Step 3
- **Register logins**: Each email with its certificate
- **4**: Step 4
- **Create the bot**: Sign-in flag, login domain

*From the Admin console to a bot that joins as a named account.*

The name and avatar shown in the meeting come from the Google account itself.

The [Google Meet page](https://meetstream.ai/integrations/google-meet) 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](https://meetstream.ai/glossary/zoom-obf) or ZAK, and Teams admission follows the tenant lobby policy.

### How many logins do I need?

About one per 20 concurrent Meet sessions.

## Keep exploring

- [Google Meet](https://meetstream.ai/integrations/google-meet): Integration
- [Meeting bot](https://meetstream.ai/glossary/meeting-bot): Glossary
- [Zoom OBF](https://meetstream.ai/glossary/zoom-obf): Glossary
- [Google Meet bot API](https://meetstream.ai/meeting-bot-api/google-meet): Product
- [Bot lifecycle](https://meetstream.ai/glossary/bot-lifecycle): Glossary
- [Google Calendar](https://meetstream.ai/integrations/google-calendar): Integration

## Put the vocabulary to work

One API to join, record, stream and transcribe meetings across Zoom, Google Meet and Microsoft Teams.

---

Full site index for agents: https://meetstream.ai/llms.txt
API contract (OpenAPI 3.1): https://meetstream.ai/openapi.json
MCP discovery: https://meetstream.ai/.well-known/mcp