A useful team bot needs access to the instructions, files and tools its colleagues rely on. It also needs to keep individual conversations private. That is the workflow behind xAI’s Team Bots launch, announced on September 28, 2026.
Team Bots are available in public beta on Teams and Enterprise plans. A team can build a Grok Bot around a role or recurring job, share it with colleagues, and invite it into a Slack channel. xAI says each person can also speak with that bot privately. Colleagues share the bot’s configuration without putting every exchange into a group chat.
One Bot Built Around a Shared Job
An account team might need one place to track customer developments; an engineering group might need help following project decisions and bug reports. Instead of having each colleague assemble a separate bot and repeatedly supply the same background, the team can give one bot access to relevant material and work from a common foundation.
People can still use the bot individually. According to xAI, it draws on shared skills while maintaining separate conversations, context and memories for each user. Colleagues share the bot’s role and expertise, but their one-to-one exchanges are not presented as a common team transcript.
This is a distinct release from the August 11 Grok Bot beta. That launch introduced persistent bots that could work across apps, remember conversations and run jobs while a user was away. xAI already described bots coordinating with one another and participating in group chats. The September update formalizes a bot that colleagues can share around a team workflow.
Four Building Blocks Give the Bot Its Working Knowledge
xAI describes four components of a Team Bot. Each adds a capability and raises a question about what the bot should be allowed to access.
- Context supplies files, instructions and skills. A team could give a bot internal documentation, a brand guide or instructions for handling a recurring process. This material helps it understand the work; it does not guarantee correct answers.
- Plugins connect the bot to applications. xAI names Salesforce, Notion and GitHub as examples, and says plugins can be connected by each person or configured for the whole team. A team-wide connection is a different access arrangement from each user bringing their own account.
- Credentials let the bot use third-party APIs that lack a plugin. xAI says this access is secure, but the launch announcement does not spell out every permission or administrative control. The scope of a credential matters as much as the bot’s instructions.
