Grok Bot Teams: Shared Bots, Admin Controls and Rollout

Grok Bot Teams lets a whole company use Bots together: share a Bot like you’d share a doc, bring it into Slack, and give admins control over apps, security and data. It’s included for every member on Teams plans, and Enterprise turns it on per group. In the video below I show how Grok Bot makes AI teammates real. Here’s how access, sharing and admin controls work, straight from xAI’s Teams and Enterprises docs.

Who gets Grok Bot on a team

According to the Teams and Enterprises guide:

• Teams: included for every member, and usage follows the seat. It’s on by default with no switch to turn it off.
• Enterprise: enabled from cursor.com/dashboard/bot using Manage Group Access.
• Not available under Privacy Mode (Legacy) or legacy request-based plans.

To bring people in, use Invite Team.

Sharing a Bot with your team

The shared Bots guide works like sharing a document:

• Share with your whole team or with people you invite.
• Give each person Collaborator or Manager access.
• Each person’s chat with the Bot is private.
• It uses the owner’s apps and secrets, plus your own apps after an Allow prompt.
• Usage is billed to the person it’s answering.
• Only the owner can delete it, and shared Bots always run in the cloud.

For a small business, that means one well-built sales Bot or support Bot that everyone uses, without each person rebuilding it. You can also bring it into Slack so people mention it in channels.

Before you roll it out

The guide lists the jobs to do first, especially for larger companies:

• Move off Privacy Mode (Legacy).
• Plan for static egress IPs if your tools only allow known addresses.
• Add *.*.cursorvm.com to your TLS proxy allowlist.
• Review the team policies below.

The docs also give a recommended baseline: eight steps for admins and five for members. Follow it rather than inventing your own.

Every admin control

Two notes from the docs: there’s no separate spend cap just for Grok Bot, and Conversation Insights is available on Enterprise.

Enterprise also has group settings. According to the security FAQ, a group’s Grok Bot tab can widen Cloud Agents, agent email, local execution, local egress, Auto-review, rules and setup scripts for that group’s members, but never tighten them. So set the strict rules team-wide, then open things up only for the groups that need more.

What’s new for teams in v0.78.1

The 27 October 2026 changelog has a long list of team changes:

• Who has access now lists your team or organisation, and a Team Bot can be set to Only you.
• Managers can add logins to a Team Bot’s own Vault from Configure > Tools.
• A Team Page appears in the Library, with a Pin button.
• The team dashboard groups setup scripts, files and team secrets, and adds a Security & compliance card with Download and Copy link.
• The admin page now says Shared Bots, with Manage Shared Bots and Create Bot.
• Admins can make it so only team admins can share Bots.
• Enterprise can terminate computers that have been inactive for 30 days.

Security on a shared team

All of one person’s Bots share a computer, and the security guide says not to treat separate Bots as a security boundary. Isolation between users, though, is strict. On a shared Bot in a Slack channel, it uses one shared computer and only the owner’s apps, and asks before using your accounts.

Every risky action goes through Auto Review, with Allow once, Always allow or Deny. On Enterprise, admins can enforce Auto-review for everyone and add team rules members inherit; members can add stricter rules, never weaker ones.

The recommended security baseline

For security-sensitive companies, the Teams and Enterprises guide gives a baseline. For admins, in short:

• Configure Network Controls (Enterprise); teams without a policy default to allow-all.
• Audit the connector policy before turning Grok Bot on, because any permitted connector is available to every member’s Bots.
• Turn on Enforce Auto-review before relying on team rules (Enterprise); Ask first wins when rules conflict.
• Set Execution on Local Computer to Never allow unless Bots need members’ machines.
• Turn off Cloud Agent delegation if you don’t need it, and keep public template sharing off.
• Add team Auto-review rules (Enterprise): production deployments, external email, payments and accepting legal terms are good Ask first examples.
• Gate sign-in to managed devices through your identity provider, since Grok Bot sign-in uses your SSO.

For members:

• Never paste credentials into chat; use the masked secret request.
• Prefer Allow once over Always allow for anything touching accounts, money or shared resources.
• Sign the Bot into accounts sized to the task, and sign it out of ones it no longer needs.
• Start new Bots on read-only tasks and drafts, keeping sending, publishing, buying and deleting behind approval.
• Review connected apps and routines regularly, and pause a routine when the system it reads from changes.

My rollout advice

Start with one shared Bot for one job, like answering common customer questions from your docs. Give one person Manager access, connect only the apps it needs on the owner’s account, and turn on Action Recording and audit logs from day one. Add more Bots once the first one earns its place.

About Julian Goldie

I’m Julian Goldie — founder of Goldie Agency and the AI Profit Boardroom. I test new AI agents almost every day on my channel, including Grok Bot, and show business owners how to put them to work. Claim your free strategy session or join the AI Profit Boardroom.

Want another angle? Read the AI Profit Boardroom guide to Grok Bot Teams.

FAQ: grok bot teams

Is Grok Bot included on Teams plans?

Yes. The docs say it’s included for every member on Teams, usage follows the seat, and it’s on by default. Enterprise turns it on per group.

How do I share a Grok Bot with my team?

Share it like a doc, with the whole team or invited people, as Collaborator or Manager. Each person’s chat is private, and usage is billed to the person it answers.

Can admins block apps for Grok Bot?

Yes. The connector policy controls which apps are allowed, and an MCP allowlist is available on Enterprise. Blocked apps show Disabled by team admin.

Is there a spend cap for Grok Bot on teams?

The docs say there is no separate Grok Bot spend cap.

Who can delete a shared Bot?

Only the owner.

Can admins stop Bots running commands on staff laptops?

Yes. Execution on Local Computer is a team control, and the recommended baseline is Never allow unless Bots need to act on member machines.

Related reading

• What Is Grok Bot?
• ChatGPT Dots vs Grok Bot
• Grok Bot vs Paperclip

Last updated October 2026. This page is a living guide to grok bot teams — the facts here move fast and it is updated as they do.