How this helps you
Everyone's Bots get the same verified answer from one controlled place, so sensitive numbers and wording stay consistent and auditable.
From now on, whenever a task needs [client exposure and positions], don't work it out yourself. Message the [Exposure and Positions] Team Bot, ask it for the verified numbers, and use only what it returns. Show me which Bot the numbers came from. If it can't answer, tell me instead of estimating.
Fill in: [client exposure and positions]: the sensitive data or check. [Exposure and Positions]: the name of your governed Team Bot.
What they did
In the official financial services workshop, Hugo Charré (Lead Field Engineer at SpaceXSI) showed a wealth management setup. Personal Bots belong to individual managing directors. Team Bots belong to the firm and are managed by an admin, who builds the skills and routines into them so everyone works from the same base. His Exposure and Positions Team Bot is the only route to position data: it connects read-only to the firm's portfolio system, holds its keys in the Vault, uses service accounts, and can reach internal tools with no API by using its own computer's browser. A second Team Bot, Comms Policy, checks client notes against approved language and routes issues to compliance for human review. In the demo, the MD asks her chief of staff which clients hold a downgraded bond; the chief of staff messages the Exposure Team Bot, which pulls the holdings from the internal system, and other Bots draft the call order and investment committee memo. His reason: if everyone builds their own exposure skill, every person computes it differently, which is a risk.
Who it's for: Team admins in finance, legal, ops or any team where one wrong number or phrase is costly.
Before you start
- A Grok Bot team plan with admin rights.
- Read-only access (service account or API key) to the system that holds the sensitive data.
How to try it
- Pick one workflow where the numbers or wording must be the same for everyone.
- As an admin, create a Team Bot for it, store its keys in the Vault and give it read-only access only.
- Write the workflow into the Team Bot as a skill, plus any routine it needs.
- Share it with the people or team who need it (you can now share to your team or whole organization and pin it in the Library).
- Tell each personal or chief of staff Bot to always ask this Team Bot for that data, and never compute it itself. Check its work by opening the Team Bot's own chat.
What to expect
Asked a question about the data, your chief of staff messages the Team Bot, which works in the internal system and returns the figures (with a screenshot in the demo), and the answer names where the numbers came from.
Common mistakes
- Letting each person build their own version of the same check. That's the risk this pattern removes.
- Giving the Team Bot write access when it only needs to read.
- Forgetting the human review step for regulated wording; the demo routes Comms Policy issues to compliance.
Related tips
- Turn a Bot into a team Bot your colleagues can use: Share a working Bot with your team as an internal tool, with owners who edit and users who just use it.
- Roll out Grok Bot to a team with admin guardrails: From the official admin video: set team rules, auto-review, plugin and network allow lists, then start with a pilot group before inviting everyone.
- How to trust your Bot's work more: Put most of your effort at the top: code structure, then lint/tests/CI, then prose rules, then human review.
Worth knowingCarved from a segment of this video starting at 9:18. Paraphrased by us; watch the original for the full walkthrough.
Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot multi-bot setups tips