Grok Bot teams means publishing one Bot that your whole team can chat with, in the app or in Slack, with each person in their own private conversation. xAI launched this as Team Bots in v0.61.0 on 26 September 2026, and the docs now call them Shared Bots. Owners decide who gets access, Managers can change how the Bot works, and admins control the rest from a dashboard.
📺 Watch: Grok Shared Bots are INSANE!
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside
If you run a small team, this is the feature that turns Grok Bot from a personal assistant into a shared teammate. Here's how sharing works, who can do what, how the team Vault works, what admins control, and what the changelog says about Microsoft Teams.
What Grok Bot teams can do
The v0.61.0 release laid out the basics. You publish one Bot for the team. Teammates chat with it in the app or in Slack. Each conversation is separate, and the Bot keeps private notes per person.
The Shared Bots docs, last updated 28 October 2026, fill in the details:
- Chats stay private. The owner and Managers can't read your chats with the Bot.
- Team memory is announced. The Bot can save things it learns for the whole team, and tells you when it does. Things about you personally stay between you and the Bot.
- Usage is per person. A reply uses the usage of the person it's answering, in the app and in Slack.
- Shared Bots run in the cloud. A Bot that runs on your own computer can't be shared.
Since v0.77.0 (26 October 2026), linked teammates use their own connectors and memory, and you can DM a Team Bot to message other Team Bots.
Building an AI team for your business but want it on an open stack? The AI Profit Boardroom ($69/mo) includes the Agent OS built on Hermes Agent, with step-by-step setups, daily tutorials and live coaching calls each week.
Roles: owner, Manager, Collaborator
Every shared Bot has three kinds of people around it. This is the one table on this page, so it's worth a slow read.
| Role | Can chat | Can change the Bot | Can delete it |
|---|---|---|---|
| Owner | Yes | Name, description, instructions, plugins, secrets, skills, files, Slack app, sharing | Yes, for the whole team |
| Manager (added from v0.64.0) | Yes | Instructions, skills, memory, apps, and logins in the Bot's own Vault (v0.78.1) | No |
| Collaborator | Yes | No | No |
| Team admin | If shared with them | Who has access and Auto-add, from the dashboard | Yes, from Manage Shared Bots |
Deleting a shared Bot can't be undone. The docs say teammates lose the Bot along with their chats and routines on it. Owners who only want to pause sharing can choose Unpublish instead, which v0.61.0 added.
📺 Watch: Hermes Bot Mode DESTROYS Grok Bot? (FREE!)
Sharing controls
Click the Bot's name, choose Share, and pick who has access:
- Your team shares it with everyone.
- People you invite limits it to the people and groups you add.
- Only you keeps it to yourself. v0.78.1 (27 October 2026) added this option for Team Bots.
Also in v0.78.1, Share and Who has access now list both your team and your organization. Admins got a "Shared Bots" admin page too.
Before you share, check the Bot's plugins, secrets, skills and files. The docs say they work in every teammate's chat. Only add keys you're happy for everyone to use.
One safety detail stands out. In your own chat, a shared Bot can use your apps, but it asks first with Allow once, Always allow or Skip. In Slack channels and threads, it uses only the owner's apps. And since v0.77.0, people without a linked account can't use the owner's logins or private data.
Team Vault logins
This one landed in v0.78.1. Managers can add logins to a Team Bot's own Vault under Configure, Tools, and the Bot signs in for the team.
Why that matters for a small business: you no longer need each person to log the Bot into the same supplier portal or booking site. One Manager adds the login once. The Bot uses it for everyone who chats with it. The Vault docs say a Bot never sees a saved password, card number or security code.
Want help deciding which logins and tools belong on a shared team Bot? Book a free AI strategy session and we'll plan the setup with you.
📺 Watch: OpenMausBot DESTROYS Grok Bot?
The team dashboard
The dashboard started with a Setup Checklist. v0.31.0 and v0.55.0 built it out to cover plugins, Slack or Microsoft Teams, GitHub, sign-in, inviting teammates and network setup.
v0.78.1 reorganized it. Setup scripts, setup files and team secrets are grouped together, and a Security and compliance card sits on the page. Members never see this admin page.
Day to day, admins use it to:
- Invite members with Invite Team
- Set Team Rules every member's Bots must follow
- Choose whether members can publish Bot templates publicly, to the team, or not at all (v0.77.0)
- Set Page sharing to anyone on the team, specific teammates, or off
- Limit sharing to admins only (v0.77.0)
- Auto-add a shared Bot to everyone's sidebar, which members then can't hide
Enterprise controls
The teams docs mark a long list of settings as Enterprise only. The main ones:
- Audit logs for Bot creation, access changes, Slack links and routines.
- Action Recording, which logs what a Bot did. The changelog notes it redacts card numbers and tokens.
- Trusted CA certificates for private servers.
- Network Controls to limit which sites team computers can reach.
- Enforce Auto-review and team Auto-review rules, so risky actions always ask first.
- Terminate Inactive Computers after 30 days without a message, plus bulk Recreate, Terminate and Delete.
- Team Secrets that setup scripts read as environment variables.
The docs also say there's no separate Grok Bot spend cap today. Account-level on-demand controls apply. And since v0.75.5 (23 October 2026), Grok Business seat admins can connect the team.
Grok Bot in Microsoft Teams
Microsoft Teams shows up in the changelog in two places only:
- v0.17.0 (12 August 2026) lets a routine start from a Microsoft Teams message.
- v0.55.0 (16 September 2026) put Slack or Microsoft Teams on the dashboard Setup Checklist.
Most of the shared-Bot features, like threads, Review an action cards and user-group mentions, are written for Slack. xAI hasn't published the same detail for Microsoft Teams. Our Grok Bot Slack guide covers the Slack side, and the Grok Bot routines guide covers the Teams trigger.
Grok Bot teams vs an open alternative
Shared Bots are strong on admin control. The trade is that your team's Bots, memory and logins live on one vendor's cloud, billed per seat's usage.
Hermes Agent gives you multi-agent teams on your own setup, with the model of your choice. See how they stack up in Grok Bot vs Hermes, or compare another rival in ChatGPT Dots vs Grok Bot. The Agent OS guide shows the full open setup, and the Goldie Bench shows which models hold up in agent work.
For the setups, prompts and weekly coaching, join the AI Profit Boardroom.
FAQ
Can the owner read my chats with a Team Bot?
No. The Shared Bots docs say each person's chat is private. The owner and Managers can't read it, and you can't read theirs.
Whose usage does a Team Bot spend?
The usage of the person it's answering, in your own chat, in Slack and in group chats. The owner's usage covers the owner's messages and Slack posts from apps or workflows not linked to an account.
What's the difference between a shared Bot and a Bot template?
A shared Bot's link opens the same Bot for everyone. A template gives each person their own copy. Admins decide whether members can publish templates publicly, to the team or not at all.
Ready to give your team an AI teammate that actually gets work done? Book a free AI strategy session, or claim your free strategy call and we'll plan your Grok Bot teams setup together.
