Teamwork · Shared methods
Grok Team Bots: what does a team actually share?
Brand materials and review methods can be reused across a team. Private chats, account access and final approval still have separate boundaries.
Based on the September 28 announcement and documentation updated October 2, SpaceXAI’s marketing workflow illustrates how one team method can be shared.

A shared Bot does not expose private chats
Each person has their own conversation; the owner cannot read teammates’ private chats. A fact enters team memory when someone explicitly says it belongs to the team. A process taught privately remains in that person’s notes until the owner saves it as a team skill. Slack channel threads, however, are shared conversations.
Sources and further reading
- Team Bots: shared and personal boundariesOfficial documentation · updated October 2Team skills, private chats and notes, OAuth and team credentials, and Slack computer scope.
Prepare a preview, then ask a person to sign off
SpaceXAI’s marketing example starts with brand guides, past blog posts and social copy. A draft arrives in Slack; Marketing Bot reviews its voice and current messaging. Reviewed website changes become edits and a preview link for human sign-off. The shared method connects references to review without removing the person’s decision. The Den offers a related pattern: AI prepares material, and people check and complete the application.
- Read the linked Marketing Bot role profileA public template profile, not a customer deliverable or outcome.
- Next: The Den returns gathered material for team review
Sources and further reading
- Team Bots announcement and marketing workflowVendor example · September 28Brand references, Slack review, preview links and human sign-off; not independent customer-outcome verification.
- Marketing Bot template linked by the announcementPublic role profile · AryamanA public role profile by Aryaman, linked from the announcement, describing the Bot’s responsibilities.

