Grok Bot 1.0 joins your meetings: Team Bots for Slack, Teams, Zoom and Meet

Grok Bot 1.0 Can Join Your Zoom, Teams and Slack: What Shared Team Bots Do and What Admins Should Check

Grok Bot 1.0 turns xAI’s assistant from a one-person helper into something a whole team can share. A Team Bot can now sit in Slack and Microsoft Teams, join Zoom, Google Meet and Teams calls, and write up the action items afterward. It’s limited to paid team plans, and two default settings deserve a look before you switch it on.

Here’s the short version, so you can decide whether the rest is worth your time:

  • Team Bots, Slack and Microsoft Teams support are on Team and Enterprise plans.
  • Meeting support (Google Meet, Zoom, Teams) is on Team, Enterprise and Ultra.
  • The Teams and meetings features arrived in version 1.0.1 on November 11, per the changelog.
  • The bot posts in the meeting chat. It doesn’t speak yet.
  • No prices or usage limits have been published.

The details below come from xAI’s changelog as summarized by developer Flavio Copes, plus UC Today’s coverage. Where a claim comes only from xAI, I’ve said so.

What Grok Bot 1.0 changes for teams

Until now, a Grok Bot was yours alone. Version 1.0 lets the person who built a bot publish it to a team, an organization, or a hand-picked list of people. A new Team Bot starts as a draft that only its creator can see, and nothing is shared until the owner clicks Publish.

That draft step matters. It gives you a place to test what the bot can reach before a colleague asks it something and it quietly uses your connected apps.

Sharing comes with three roles, and the differences are worth knowing before you hand them out:

  • Collaborator: can chat with the bot.
  • Manager: can chat, change how the bot works, and share it.
  • Owner: can do all of that and delete the bot.

One privacy detail stands out. According to Copes, each teammate’s chat with a Team Bot stays private, and owners and managers can’t read it.

How the bot joins Slack, Teams and meetings

Slack worked during the beta. Microsoft Teams is the new piece, and setup takes three steps: a team admin turns it on, the bot’s owner or a manager connects it, and then a Teams admin approves the app in the Teams admin center. Microsoft doesn’t notify that admin, and Copes notes it can take up to an hour after approval before things work.

Each person also links their own Microsoft account once. xAI’s connector documentation says Grok can only reach teams, channels and chats the signed-in person already belongs to.

Meetings work a little differently. The bot joins Google Meet, Zoom or Teams calls after the host admits it, and its name shows “transcribing” so everyone can see it’s there. You can ask it questions or assign action items in the meeting chat, and it posts a summary when the call ends.

Live spoken back-and-forth is listed as “coming soon,” so don’t expect a voice in the room yet. If you connect a calendar, the bot can also join scheduled meetings by itself.

The shared-login setting admins should check

The riskiest choice isn’t the bot itself. It’s whose accounts the bot uses when it touches your other apps. For each connected app, the owner picks one of three modes, and the mode decides who gets blamed when something goes wrong.

Mode Whose access the bot uses What to watch
Use individual accounts Each teammate connects their own account Safest default. Everyone sees only what they could already see.
Share your account All teammates act through the owner’s account Actions are attributed to the owner. Needs a team admin to enable Allow Shared Logins, which is off by default.
The bot’s own account A separate team account Not offered for every app.

There’s a second default to check. Copes reports that Slack Workspace Access is on by default, so people outside your team can use organization-shared bots, and their usage counts against your team’s allowance.

Admins can also limit bot sharing to admins only, and switch meetings off under Bot Capabilities. Existing shares stay in place when you tighten sharing, so review them by hand.

Does it really act on its own?

xAI’s announcement leans on initiative: the main bot looks for work it can take over and offers to do it. The documentation is more modest, according to Copes. It describes the bot asking before risky actions and telling you when an app has signed you out.

One quirk may annoy some teams. Copes says you can’t turn the check-ins off, and switching off notifications only silences the alerts.

If you’ve followed our earlier post on the Grok Bot usage limit, you’ll know capacity has been a sore spot. Shared bots will pull more usage per team, which makes the missing limits more important.

Several things are still unclear:

  • How much Team and Enterprise plans cost, and what the usage limits are.
  • How long meeting transcripts and recordings are stored.
  • Which regions get the meeting feature.
  • Whether xAI’s claim that bots carry context across conversations and share threads with other bots holds up. That one is a vendor claim, and Copes didn’t test it.

Until xAI answers the storage question, treat a meeting bot like any other recorder and tell the people on the call.

Frequently Asked Questions

Is Grok Bot 1.0 free?

Not for the team features. Team Bots, Slack and Teams sit on Team and Enterprise plans, and meetings also work on Ultra. xAI hasn’t published prices for these features.

Can Grok Bot join a Zoom or Google Meet call?

Yes, on Team, Enterprise and Ultra plans. The host has to admit it, and its name shows “transcribing.” It replies in the meeting chat rather than speaking.

Can my boss read my chats with a Team Bot?

According to Copes, no. Teammates’ chats are private, and owners and managers can’t read them. Check your own admin dashboard, since xAI’s wording could change.

Do I need admin approval to use it in Microsoft Teams?

Yes. A team admin must enable it, and a Teams admin must approve the app in the Teams admin center. Allow up to an hour after approval.

Should you roll it out?

Try it with a small group first, and only with individual accounts, until you’ve read the admin page line by line. The meeting notes are the easy win, since a bot that posts action items after a call saves real time. Leave Allow Shared Logins off and tighten Slack Workspace Access before you invite anyone outside the team, because those two defaults are where a convenient tool turns into a surprise.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *