Grok Bot Enterprise: A Step-by-Step Setup for Small Business Owners
Grok Bot Enterprise is the business side of Grok Bot: shared Team Bots your staff can all use, plus admin controls that decide what those Bots may reach and do. Most small businesses start on the Team plan and only need Enterprise once logs, provisioning and locked approval rules matter. Here’s the whole setup as an owner would do it, one step at a time.
Key takeaways
Team plan: Grok Bot is on for every member, no admin action needed.
Enterprise plan: an admin turns it on and picks which groups get it.
Team Bots: one shared Bot, a private chat for each person.
Since 11 Nov 2026: meeting notes, Microsoft Teams, shared logins, Review learnings.
Start with the plan, because it decides which switches you even see. Per the teams and enterprises docs, the Team plan bundles Grok Bot in for all members from the first day, and an admin can’t switch it off. On Enterprise, nothing runs until an admin enables it on the Grok Bot page of the Cursor dashboard.
You need…
Team
Enterprise
Shared Team Bots with private chats
Yes
Yes
Microsoft Teams and Slack connections
Yes
Yes
Bots that join calls and send notes
Yes
Yes
Turn Grok Bot on or off for the company
No
Yes
Automatic staff accounts (SCIM)
No
Yes
Website allowlists for Bots
No
Yes
Approval rules staff can’t switch off
No
Yes
Audit logs and Action Recording
No
Yes
If you buy through The X Subscription instead, the subscription page lists Grok Bot on Premium, Super and Ultra, not on Plus. Use plan names when you talk to sales, and check the plan matrix the docs link to.
Step 2: Clear the blockers before staff log in
Move off Privacy Mode (Legacy) in Team Settings. It blocks Grok Bot completely.
If your office uses a filtering proxy such as Zscaler, allow Cursor’s domains, including *.*.cursorvm.com, and exempt them from inspection.
Check your app list in the Team Marketplace. Every app you allow is open to every Bot a staff member runs.
Staff sign in with their Cursor account, so your normal company sign-in carries over. The identity guide lists Okta, Microsoft Entra, Google Workspace and OneLogin as supported for Cursor’s SAML 2.0 single sign-on.
Want shared AI Bots running safely in your business? Inside the AI Profit Boardroom you get the Agent OS — Hermes, OpenClaw, OpenCode, Claude and Codex in one place — plus step-by-step Hermes training and four live coaching calls a week.
These sit on the Grok Bot page of the dashboard, and only admins see it.
Execution on Local Computer: choose Never allow, so Bots can’t run tasks on staff laptops. The default leaves it to each person.
Bot sharing: choose Admins only while you learn what your staff build. Bots already shared stay shared.
Allow Shared Logins: leave it off. Switched on, it lets a Manager lend their own login to a Bot, and then every teammate’s request runs as that Manager.
On Enterprise, add two more: turn on Enforce Auto-review so nobody can switch the risk check off, then add team Ask first rules. Good candidates: sending email outside the business, anything involving payments, pushing changes to your live website, and agreeing to terms on your behalf.
Step 4: Build your first Team Bot
Pick one job your team repeats every week, like call notes or a client report. Then:
Choose + in the sidebar, then Create a Bot, and give it a name.
Tell it in one sentence what it helps the team with.
Add only the apps, secrets, skills and files it needs. Everything you add works in every teammate’s chat.
Press Publish when it says it’s ready. Until then, it’s a draft only you can see.
Share it from Share at the top right of its chat. Teammates you add chat as a Collaborator; give your office manager the Manager role so they can change it too. The Team Bots page confirms each person’s chat stays private, even from you as the owner.
Step 5: Approve what the Bot learns
This is the change I like most in the v1.0.1 changelog from 11 November 2026. When a teammate teaches a Team Bot something for the whole team, it no longer saves it straight away. It parks the idea under Review learnings for you or a Manager to sign off.
Open the Bot’s details once a week, read each suggestion, and press Approve or Reject. Approve only what you’d teach a new hire. What the Bot learns about each person stays private to that person.
Step 6: Bring it into Microsoft Teams and your calls
If your office runs on Microsoft Teams, three people take part. Your Cursor team admin turns on Enable Microsoft Teams. The Bot’s owner connects it from Bring to your team’s Microsoft Teams. Then a Microsoft Teams admin approves it under Pending approval, on the page Microsoft describes in its Manage apps guide. Microsoft sends that admin no alert, so forward the approval link yourself.
Calls are separate. On Team, Enterprise and Ultra plans, the meetings docs say you paste a Google Meet, Zoom or Microsoft Teams link into the Bot’s chat, approve its card, and the host lets it in. It shows up with “transcribing” in its name, so tell clients it’s there. Afterwards it posts a summary and action items in its chat.
Step 7: Know what stays out of your hands
Bots run only on hosted cloud computers in the United States. On-premises hosting isn’t supported today.
Grok Bot chooses its own model, and your team’s model allowlist doesn’t apply to it.
Each staff member gets one cloud computer for all their Bots, so anything they sign in to there, every one of their Bots can use.
Deleting a Team Bot removes it for everyone, with their chats and routines, and can’t be undone.
The security page also notes that with Privacy Mode on, customer data isn’t used for training, and that Grok Bot sits inside the ISO/IEC 27001 and ISO/IEC 42001 scope of Anysphere, the company behind Cursor.
My verdict
For a small business, the Team plan is the right first step: shared Bots, private chats, Microsoft Teams, call notes and approved learnings are all there. Move up to Enterprise when a client, an auditor or your IT person needs logs, automatic staff accounts and approval rules nobody can turn off. Start with one Bot, one weekly job and two or three staff, keep anything that sends or spends behind an Ask first rule, and grow from there. Set up that way, Grok Bot Enterprise gives your team AI help you can actually control.
About Julian Goldie
I’m Julian Goldie — founder of Goldie Agency and the AI Profit Boardroom. I test new AI agents almost every day for 432K+ YouTube subscribers and run Hermes, OpenClaw, OpenCode, Claude and Codex side by side in my own Agent OS. Claim your free strategy session or join the AI Profit Boardroom.
On the Team plan, yes: every member gets access without an admin doing anything. On Enterprise, an admin enables it and chooses which groups get it.
What does Enterprise add over the Team plan?
The company-wide on/off switch, SCIM accounts, website allowlists, setup scripts and secrets, approval rules staff can’t turn off, audit logs, Action Recording and data retention.
Can I see what my staff ask a Team Bot?
No. You can’t open your staff’s chats with a Team Bot, and they can’t open yours. Managers can’t either.
Can a Grok Bot take notes in my client meetings?
Yes. Paste the call link into its chat on a Team, Enterprise or Ultra plan; it works with Zoom, Google Meet and Microsoft Teams, and posts a summary with action items when you hang up.
Do I need a Microsoft admin to add a Bot to Teams?
Yes. A Microsoft Teams admin approves the Bot in the Teams admin center after your Cursor team admin enables Microsoft Teams and the owner connects it.
Should I turn on Allow Shared Logins?
Only if one account with nothing sensitive in it must serve everyone. With it on, the Bot does every teammate’s work under that one Manager’s login.
Ready to put Hermes to work in your business? Join the AI Profit Boardroom for the Agent OS, setup training and daily updates.
