Feature request: an admin setting on the Grok Bot team plan to control or restrict members creating their own personal bots. Team Bots with Auto-add already let us push shared bots to new employees, which is great. But people still spin up a brand new bot for nearly every chat, which creates sprawl and duplicated setup. We’d like a way for admins to limit personal bot creation (or require approval), so everyone works from the managed Team Bots instead.
We’re evaluating Grok Bot Enterprise for our organization. We’d like to give staff a locked-down setup with only 1–3 bots that an admin builds and publishes as Team Bots.
Is there an Enterprise setting that stops members from creating their own bots, so they can only use the bots an admin published? We didn’t find one in the admin docs. For us this is likely a deal-breaker, so a clear answer would help a lot.
If it isn’t available today, is it on the roadmap? Is there a workaround, such as group settings or the Admin API?
There isn’t a setting today that stops members from creating their own Bots. Any member with Grok Bot access can create personal Bots, and can also publish Team Bots of their own.
Here’s what admins can control today:
Manage Group Access (Grok Bot page in the dashboard): which members or groups can use Grok Bot at all.
Manage Team Bots: push the Team Bots you publish to the whole team or to specific groups. Members who get a Bot this way can’t hide it from their sidebar.
Per-Bot access: on each Team Bot, keep members as Collaborators (they can chat with it and use its skills), so only you and anyone you make a Manager can change its setup.
The team’s Grok Bot controls (agent capabilities, network access, enforced Auto-review) also apply to Bots members create themselves.