Grok Bot’s September 26 release introduced Team Bots. Current official documentation describes an assistant configured once with shared skills, files and tools, then used by teammates in separate conversations. Publishing makes the Bot available to the team; it is different from handing everyone an independently maintained copy of a public template.
The documentation distinguishes shared team memory from private notes for each person. Access also depends on the connection type: account-based sign-ins use the requesting person’s account, while a configured service credential can be shared by the Bot. Owners and designated managers maintain its configuration, so a shared assistant still needs somebody responsible for its setup.
Editorial take: This is useful for repeatable work with a common playbook, such as an internal helpdesk. The important setup question is which information should be shared and which belongs to one person. Before publishing, a team should review the assistant’s tools and reference material as carefully as it would review access for a new colleague.