News confirmed medium confidence

xAI Launches Shared Team Bots for Grok

The public beta lets Teams and Enterprise customers share a Grok Bot's tools and role knowledge while keeping each member's conversations and personal context separate.

Edited by Tyronne Panaino

xAI launched Team Bots on September 28, 2026, as a public beta for its Teams and Enterprise plans. The feature lets an organisation take a Grok Bot built around a role or workflow and share it across a group, while each member can still interact with the bot individually.

The release changes Grok Bot from an agent that can be configured for a single workflow into a reusable team surface. It is relevant to business users and administrators who want an agent to carry common instructions, connected tools and role knowledge across a department instead of rebuilding that setup in every conversation.

Shared role knowledge with separate user context

The Team Bots design combines four elements. Context supplies shared files, instructions and skills; plugins connect workplace applications; credentials provide access to third-party APIs that lack a plugin; and memories retain information the bot learns while doing its assigned work.

xAI says the shared bot keeps each person's conversations private and maintains separate context and memories for each user, even while drawing on common team skills. That is an important product boundary, but the launch page does not provide a detailed retention schedule, administrator audit model or connector-by-connector permission matrix. Organisations handling sensitive data will still need to verify those controls against their own policies.

Team Bots can also participate in Slack through their own handles. A team can invite a bot into a channel, ask it questions, contribute context and see its responses together. The launch page describes internal uses across account work, engineering coordination, marketing review and data analysis, showing that xAI is positioning the feature as a persistent collaborator rather than a one-off chat assistant.

The practical delta for enterprise agents

Shared agents reduce one familiar source of operational drift: different employees can otherwise maintain different prompts, tool connections and process instructions for nominally the same job. A Team Bot creates a common role definition while preserving individual conversations. That architecture could make onboarding and repeatable workflows easier, provided the shared instructions and credentials are governed carefully.

The same persistence also raises questions that the announcement does not settle. A memory that improves across use can preserve useful corrections, but administrators need to know who can change shared skills, how incorrect memories are challenged, whether a person can inspect what influenced an answer and how access changes are propagated when someone changes roles. Those are product-evaluation questions, not evidence that a failure has occurred.

Availability and evidence limits

Team Bots is available in public beta on Teams and Enterprise plans. xAI says customers can share existing Grok Bots and start from templates for sales, product management, marketing or data analytics. The company provides examples from its own workflows, but the source does not include independent adoption data, reliability measurements or a general-availability date.

Internal confidence is therefore medium. The official launch page establishes that the beta exists, who can access it and how xAI describes the feature. It does not independently validate productivity, security or outcome claims. The next useful checkpoints are a documented administration model, external customer testing and a clear path from public beta to general availability.

Status

Confirmed. xAI has launched Team Bots in public beta for Teams and Enterprise customers. Operational performance and control effectiveness remain vendor-reported or undocumented in the available source.

Sources

Update note: Last reviewed 2026-10-04. We will revise this post if xAI publishes fuller administration documentation, availability changes or independent deployment evidence emerges.

Sources

Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.

More News coverage