xAI has taken Grok Bot out of beta, and version 1.0 changes who the product is for. A Bot can now be published to a whole team and used in the app, in Slack, in Microsoft Teams, and inside Google Meet, Zoom, or Teams calls. The announcement landed November 2, and the app picked up the 1.0 number on November 11, according to developer Flavio Copes, who walked through the release on his site.
A personal assistant answers to one person. A shared Bot has to settle whose computer it runs on, whose logins it uses, and who pays, and most of 1.0 is xAI’s answer to those three questions.
A Team Bot now starts as a draft that only its creator can see. The creator walks through setup, covering connected apps, secrets, skills, and uploaded files, then clicks Publish. Access can go to the team, the whole organization, or a hand-picked list of people and groups. Collaborators can chat with the Bot, Managers can also change how it works and share it, and the Owner can delete it. Individual conversations stay private from Owners and Managers alike.
Location decides the machine. A private chat or Slack direct message uses the personal Grok Bot computer of whoever is asking. The Bot can reach the owner’s apps, plus the asker’s once an Allow card is approved. A Slack channel, thread, or group chat runs on the Bot’s shared computer and reaches only the owner’s apps. Usage lands on the person the Bot is answering, except for Slack users without a linked account, where the team pays.
Learning is now gated. In the beta, a Team Bot saved whatever teammates taught it and reported afterward. Under 1.0 it proposes the change and waits. Owners and Managers open a Review learnings list, where each item names its effect (updating a skill, for example) and carries Approve and Reject buttons. Instructions an Owner or Manager types into the main chat still take effect immediately. A Manage screen also adds analytics: message volume, time saved, and the heaviest users.
Microsoft Teams is the new channel, and it takes three separate approvals. A team admin enables it from the dashboard with a Microsoft Teams or Global administrator account. The Bot’s Owner or a Manager then connects it. Finally a Microsoft Teams admin approves the Bot in the Teams admin center. Microsoft does not notify that last admin, so the Owner has to send the link by hand, and the Teams side may need as long as sixty minutes to finish.
Meetings work on Meet, Zoom, and Teams, and they are open to Ultra subscribers as well as teams. The user pastes a link, approves a card, and the host admits the Bot, which joins under a name showing who it belongs to. It does not speak. People write to it in the meeting chat, and when the call ends it posts a summary and action items. xAI says live back-and-forth conversation is coming. Its own team keeps a Bot in the daily standup, writing notes to a shared Google Doc.
Shared connectors carry the sharpest trade-off. For each app, the Owner or a Manager picks one of three modes: every teammate connects an individual account, the Owner’s account is shared, or the Bot uses a separate team account (not every app supports that last option). Sharing the Owner’s account requires an admin to flip Allow Shared Logins, which ships switched off. Copes flags the consequence: every action the Bot performs in that app, whichever colleague asked, runs under the Owner’s identity. The app’s own records will therefore credit a colleague’s request to one person.
Admins get four more controls. Bot sharing can be limited to admins. Meetings can be disabled for every Bot. A Manage Bots list shows each shared Bot, with an option to add it to members’ sidebars automatically. Slack Workspace Access, on by default, lets people in a Slack workspace who are outside the team use Bots shared with the organization, and their replies count against the team’s usage.
Plan limits are firm. Team Bots, Slack, Microsoft Teams, shared connectors, Review learnings, and analytics need a Team or Enterprise plan. Individual users get a faster browser, better documents and slides, and fewer approval prompts. Copes runs his Bots alone, so his team steps follow xAI’s documentation rather than hands-on testing, and his Mac app was still on version 0.79.3 the evening the 1.0 entry appeared in the changelog. The walkthrough contains no measurements of how the Bot performs for a working team.
Any team that turns on organization-wide sharing should check Slack Workspace Access first, because its default quietly lets outsiders in the workspace spend the team’s usage.
Reported by Flavio Copes on flaviocopes.com on November 11, 2026.
