How do you let the whole team share one Grok Bot?
Xiao Lin from the marketing department taught her Bot the brand voice, banned words, and commonly used materials one by one, and the copy it produced finally looked decent. The next day, Xiao Zhou from the same team wanted an assistant like that too, so she had to teach it all over again from scratch; on the third day, Xiao Lin's Bot still didn't know the new rules Xiao Zhou had taught.
This is exactly the problem that the headline feature of Grok Bot 1.0 (released in 2026-11-11) is meant to solve. First, answer a question to see whether you can tell the two kinds of "sharing" apart:
Quiz timeXiao Lin wants the whole team to talk to the same copywriting Bot, so that whoever teaches it a new rule, everyone benefits. Which approach should he use?
A Team Bot is the same Grok Bot shared with the team: everyone uses the same set of apps, secrets, skills, and files, and each person's chats with it are not visible to the others. The official recommendation is to treat it as an internal tool: one Bot does only one thing, such as a Launch Bot that tracks release cadence, a Copy Bot that writes copy in the brand voice, or a Research Bot that answers user interview questions.
What you'll be able to do after learning
- Create a Team Bot, publish and share it with the team, and assign the three roles of Owner, Manager, and Collaborator
- Review what colleagues teach it and decide which items become rules for the whole team
- Connect it to Slack or Microsoft Teams, and clarify who the usage and computer are attributed to
First, confirm you can use it
Team Bot has two prerequisites:
- Your plan is Team or Enterprise (individual plans don't have this feature).
- There is at least one other person on the team.
Also, Team Bots run in the cloud, so a Bot running on your own computer can only be a personal Bot. Team admins can also set Bot sharing to Admins only, in which case regular members will see Only team admins can share Bots and the share button is grayed out.
- My plan is Team or Enterprise, and under + in the sidebar I can see Browse Team Bots
Step 1: Create a Team Bot and publish it
Why: everything you put in is available to everyone it's shared with. So from the moment you create it, only include things everyone is allowed to use.
- 1?
- 2?
- 3?
- 4?
Click them one by one, in order.
Already have a Bot you want to share? First check its apps, secrets, skills, and files, then select Share directly (see step 2).
You should see: the Bot changes from Draft to published; colleagues can find it in Browse Team Bots.
- My Team Bot is published, and it contains no accounts or files the whole team shouldn't use
Step 2: Share it with colleagues and assign roles
Why: who can use it and who can change it determines whether this Bot will get messed up.
- In the top-right corner of the Bot chat, select Share.
- In Who has access, choose: your team, Everyone in your organization, or People you invite.
- To invite specific people, add them in Add people or groups.
- To let someone change it, open that person's role and select Manager.
- To send a link, select Copy link.
The division of duties among the three roles:
| Role | What they can do |
|---|---|
| Owner | Can do everything a Manager can do, and can also delete the Bot. Whoever creates it is the Owner |
| Manager | Change the Bot's settings, review what it learns, share it |
| Collaborator | Chat with the Bot, teach it things |
A Bot can have any number of Managers. The official recommendation is to add at least one more Manager so that content awaiting review doesn't all get stuck with one person. To stop sharing, select Only you; only the Owner can do this.
You should see: Share lists the people with access and their roles.
- At least two people are Managers (including the Owner)
Step 3: Colleagues find and use it
Why: sharing only grants permission; colleagues still need to add the Bot to their own sidebar.
Coworkers do this: in the sidebar + → Browse Team Bots (on desktop you can also press Cmd/Ctrl+K and select it), then choose Add. At the top of the list is Popular; ones with the Team approved badge have been endorsed by team admins. They can also just ask their own Bot "Is there a Team Bot for release planning?", or open the link you sent.
On desktop, coworkers can also have voice conversations with a Team Bot, or pull it and other cloud Bots into the same group chat.
You should see: the Bot appears in the coworker's sidebar; you can't see their chats with it, and they can't see yours.
- At least one coworker has chatted with this Bot from their own sidebar
Step 4: Review what it has learned
Why: team memory is shared, so what one person teaches changes the Bot for everyone, which is why someone needs to gatekeep it.
When a Collaborator teaches it "from now on, the whole team does it this way", the Bot only stores a suggestion first and must wait for an Owner or Manager to approve. What an Owner or Manager teaches takes effect immediately. Personal habits it learns from you stay only in your own chats.
- Open the Bot's details and choose Review learnings, which opens Knowledge.
- Under To review, choose Approve or Reject for each suggestion.
You should see: approved suggestions appear under Recently learned.
- I reviewed a suggestion a coworker taught it
Step 5: Connect it to Slack
Why: the team usually talks in Slack, so that's where the Bot is most handy.
Share first, then connect. As an Owner or Manager:
- Open the Bot's details and find Bring to your team's Slack.
- Choose Connect. If it shows Awaiting admin approval, ask your Slack workspace admin to approve this app.
Once connected, each coworker must link their own Slack account once per workspace so the Bot knows who is who: when the Bot prompts, click Connect, or go to Settings → General → Team Bots and click Link. In threads, the Bot works on behalf of the coworker who @-mentioned it, and can even hand tasks to that coworker's own Bot.
Who can talk to it in Slack depends on who you shared it with:
- Shared with the whole organization: all full members of the Slack workspace can @-mention it, even without linking an account or having a seat—only some features are limited, and they must link before direct messaging.
- Shared with a team or specific people: only those people can use it.
- Slack guests, Slack Connect channels, and other workspaces cannot use Team Bots.
You should see: the Bot's details show Connected, and coworkers can direct-message it or @-mention it in channels.
- I @-mentioned it in a channel and it replied in the same thread
Step 6: Connect it to Microsoft Teams
Why: teams that use Teams can do this too, but there are two extra admin gates to pass.
- A team admin enables it first: on the dashboard's Grok Bots page, under Shared Bots, choose Enable next to Enable Microsoft Teams, sign in with a Microsoft Teams or global admin account, and consent to the permissions.
- An Owner or Manager connects: the Bot must already be published. In the Bot's details, find Bring to your team's Microsoft Teams, choose Connect Microsoft Teams, and sign in to your Microsoft account in the browser.
- A Teams admin approves: when the dialog shows Waiting on admin approval, the Teams admin must approve it in the Teams admin center under Teams apps → Manage apps → Pending approval. Microsoft won't notify them, so you need to send them the link from the dialog; after approval, click Check again.
When a coworker messages it for the first time, they'll receive a Link Account card visible only to them; clicking it to sign in to their Microsoft account is enough. They can also link in advance under Settings → General → Team Bots.
You should see: after approval, Microsoft Teams completes the setup on its own, which can take up to an hour; afterwards the dialog shows the Bot is in Teams, and Open in Teams appears. To use it in channels, you also need to add it to a team in Teams.
- I @-mentioned it in a Teams channel or group chat and it replied
Whose usage, computer, and account it counts as
| Your own chats, Slack direct messages | Shared chats (Slack channels, threads, group direct messages, group chats in the app) | |
|---|---|---|
| Which computer is used | Your Grok Bot computer | One shared computer of the Bot's own |
| Whose usage it counts as | You | The person it is currently answering |
| Who clicks the approval card | You | Only the person it is currently answering |
In shared chats, the Bot never works on your computer, so nothing on your computer appears in channels. When replying in Slack to someone who hasn't linked an account, or to someone outside the team, it uses the team's usage.
As for accounts, a Team Bot uses the apps and secrets the Owner added. In your own chats, it can also use your apps, but it first pops up an Allow card to ask you; in shared chats, it likewise asks first before using your account. It cannot use your personal Vault—to give it keys, use Secrets. To make all Team Bots ask again, go to Settings → General → Team Bots and choose Clear connector preferences.
Quiz timeIn a Slack channel, Xiao Zhou @-mentioned the Team Bot Xiao Lin created and asked it to compile some materials. Whose usage does this count against?
Be extra careful when sharing an account. There is one exception that lets a Bot stop acting "only on your behalf": the shared connector. A team admin first turns on Allow Shared Logins (off by default), then the Owner or Manager goes to Setup in the Bot's details, then to Service accounts, picks an app in Shared connectors, and chooses Use individual accounts (each person connects their own) or Share your account (everyone acts through your account). If you choose the latter, anyone who talks to the Bot can act as that account, including making changes. The official advice: only share accounts that contain no sensitive content.
- I can explain who usage and approvals are attributed to in a shared chat
Checkpoint
- My Team Bot is published and colleagues can find it in Browse Team Bots
- I can explain what Owners, Managers, and Collaborators can each do
- I know that team rules taught by a Collaborator only take effect after approval via Review learnings
- I know that Slack guests and Slack Connect channels cannot use Team Bots
- I know that usage in a shared chat is attributed to the person being answered
Didn't work?
Look it upCommon Team Bot errors
Click one to see.
Assuming Team Bots and templates are the same thing. A template gives each person a copy, and their Bots don't affect each other; a Team Bot's link opens the same Bot. If you want copies, see Bot templates.
Assuming deletion only affects yourself. Deleting a Team Bot removes the whole team's entry point along with everyone's chats with it. Only the Owner can delete it: right-click it in the sidebar and choose Delete.
Attaching a sensitive account to a Team Bot. It works for every teammate using the Owner's apps and secrets. Only attach things that everyone sharing it may use; for the admin-side switches, see Team setup.
Next section
For how Team Bots work with group chats and handoffs, revisit Multi-Bot collaboration; to put Bots to work in specific tasks, go to Scenarios in practice: choose your path.