Grok Bot’s Team Bots guide describes a boundary that matters when turning a personal workflow into a team service. A routine belongs to the person who created it, runs as that person and reports in their chat. Only that person can see or change it. Sharing the Bot’s configuration therefore does not create one team-wide recurring job.
The guide says a routine can post results to a shared destination, such as Slack, and its usage counts against its creator’s allowance. When copying a personal Bot into a Team Bot, users choose whether routines move or remain with the personal Bot; either way, they still run for that user. These are documented conditions in guidance revised October 8, not a new release or independently tested behavior.
Editorial take: Before relying on a shared assistant for a recurring report, record three things: who owns the schedule, whose account runs it and where colleagues receive the result. Sharing an output is different from sharing control of the job. A visible owner and a documented handover plan make it easier to maintain the workflow when responsibilities change.