Signed in bots login to a user account for the meeting platform before joining the meeting. By default, bots are not associated with a specific user account, they're doing the equivalent of opening an incognito window and navigating to the meeting URL.

Why Use Signed In Bots?Copied!

• Appearance: Signed-in bots appear as a normal user rather than an anonymous one, so they have an avatar and don't have the 'Unverified' labels that some meeting platforms add for anonymous users.
• Access: Some meetings are configured to not allow anonymous users to join at all. In these cases, a signed-in bot is required to join the meeting.

The downsides of signed in bots are that it will take slightly longer to join the meeting and there is some setup work required.

Signed in Teams BotsCopied!

We currently support signed-in bots for Microsoft Teams. Here's how to set it up:

1. Create a new Microsoft Office365 organization to hold the bot's account. You must disable two-factor authentication (2FA) on this organization so that the bot can log in with only an email and password. To disable 2FA, please disable security defaults, following the instructions here. After 2FA is disabled, create a new account in the organization for the bot. If you encounter any issues with this step, please reach out to us on Slack.
2. Navigate to the Settings -> Credentials page, scroll down to Teams Bot Login Credentials and add the email and password for the bot's account in the organization you created.
3. When calling the create bot endpoint, you must pass the following parameter to instruct the bot to use the stored credentials to sign in before joining: "teams_settings": {"use_login": true}.

Sign in Bots for Other PlatformsCopied!

Currently, we do not support signed-in bots for platforms other than Microsoft Teams.