The call
Start with one team on Premium seats, with connectors, sharing, and spend limits set in advance, and expand only on the Usage tab's numbers.
Choose the plan by the admin controls your security review requires. Finish the admin setup while the workspace is still empty, so the first people to join find their work apps connected and spending already limited.
When you need this
Roll it out
Before rollout: plan and controls
Which controls does your security review require?
What good looks likeOrganizations tied to your email domain, SSO through your identity provider, SCIM, and custom retention need Enterprise. Self-serve team plans give centralized billing and usage analytics. SCIM activation can add or remove access, so check the console's summary of who gains or loses access before you activate it.
Before rollout: data handling
Which data controls apply to the plan you buy?
What good looks likeTeam workspaces on Grok Business carry xAI's enterprise terms, and members keep a personal workspace unless an Enterprise license disables it. On grok.com, an improve-the-model toggle in data controls decides whether Build mode chats and build sessions can be used for product and model improvement. API requests are kept 30 days for abuse review and are not used for training.
During the pilot: connectors
Which company systems should Grok reach, and through whose account?
What good looks likeOn Business and Enterprise, an admin adds each connector in console.x.ai, and members then connect their own accounts. Microsoft connectors need admin consent. A custom MCP server must be reachable over the public internet.
Before expanding: spend and sharing
What stops a heavy user from running up the bill, and how far can members share?
What good looks likeSet the monthly additional usage limit as a fixed amount or per seat, and leave Auto Top-up off until the pilot ends. Set a sharing ceiling for each resource type in Sharing & Retention, since conversations and projects default to organization-wide sharing.
Questions for the owner
- Which terms govern team conversations on The X Subscription team plans, and do they match Grok Business?
- Who holds Billing Read-Write and Team Read-Write permissions in console.x.ai?
- Should personal workspaces stay available to members, and does that need an Enterprise license to change?
- Which members need Super or Ultra seats, judged by their Usage tab breakdown?
Red flags
- Auto Top-up turned on with no monthly additional usage limit.
- Public conversation links allowed by policy in a team that handles customer data.
- A Grok Business team switched to The X Subscription before anyone confirmed the terms, since the switch is permanent.
- SCIM activated before anyone reviewed who gains or loses access.
Products in this piece
Sources
- Official documentation
- 9
- xAI docs: Grok.com User Guide (Grok Business)
- xAI docs: Grok Business license and user management
- xAI docs: Grok Business connector management
- xAI docs: Grok Enterprise organization management
- xAI docs: Grok connectors
- xAI docs: Team plans, workspaces, seats, and invites
- xAI docs: Spending caps and alerts
- xAI docs: Extra usage credits and top-ups
- xAI docs: Security FAQ