Grok Bot lets Enterprise team admins recreate or terminate Bot computers in bulk
1 month ago
Grok Bot team admins on Enterprise can now recreate or terminate their members' Bot computers in bulk, restart them after a settings change, and terminate computers left unused for 30 days. A new switch also turns off Messaging Between Bots. https://docs.x.ai/grok-bot/computers https://docs.x.ai/grok-bot/security-faq https://docs.x.ai/grok-bot/chat-and-collaboration https://docs.x.ai/developers/release-notes.md
Ask about this presentation
Chapters
Show transcriptHide transcript
Team admins on an Enterprise team can now manage their members' Grok Bot computers, alongside organization admins. Manage Bot Computers, on the Grok Bot dashboard page, recreates or terminates computers for many members at once.
Both actions keep each member's durable disk, so their Bots, files and logins come back. Recreate moves them to the latest image and runs Team Setup again. Terminate stops the work, and their next message starts a fresh computer.
Either action removes apps and packages members installed themselves. Anything Team Setup installs comes back. A terminate loses the turn that was running, and a recreate can drop sign-ins to company tools.
After some team settings change, the Grok Bot page shows a restart notice. Enterprise team admins can run that restart themselves. It recreates every member's computer with the current settings. Terminate and delete stay under Manage Bot Computers.
Terminate Inactive Computers cleans up idle computers, and it's off by default. Turned on, it terminates any computer unused for 30 days, including ones already past that mark. A computer with a Bot at work is left alone.
Terminating a computer, by hand or automatically, only ends the member's current work. To remove access, take the member off the team or turn off their access with Manage Group Access, then revoke their sessions in your identity provider.
A team admin can also turn off Messaging Between Bots, which is on by default. While it's off, members' Bots can't message other Bots or hand them work, and other Bots can't message them.
Up next
1:52Grok Bot's Vault lets Bots sign in and pay without seeing your passwords
@grok-bot
1 day ago
1:06Grok Bot now acts only as you, and keeps your passwords out of the model
@grok-bot
1 day ago
2:29Grok Bot now signs in with Okta FastPass on its own computers
@grok-bot
2 days ago
2:19Grok Bot now shares one Bot with your whole team, in Slack and Teams
@grok-bot
2 days ago
1:59Grok Bot Team Bots now learn for the team and join Microsoft Teams
@grok-bot
3 days ago
1:56Grok Bot buys your conference pass from memory and asks before it emails finance
@grok-bot
1 week ago
1:04Grok Bot now shuts idle computers after 30 days without a message
@grok-bot
1 week ago
2:17Grok Bot inference hooks let your security server block a prompt before the model sees it
@grok-bot
3 weeks ago
1:58Grok Bot admins can now wipe a member's Bots and data in one step
@grok-bot
3 weeks ago
2:52Grok Bot now deploys to your whole organization with Jamf, Intune and Ansible
@grok-bot
1 month ago
1:19Grok Bot plugins now install from Connect apps
@grok-bot
1 month ago
1:43Grok Bot Team Bots get managers, and Bots can read X
@grok-bot
1 month ago







