Grok Bot Vault lets a small business hand its AI agent the keys to supplier portals, booking systems and checkout pages without the agent ever reading a password or card number.
That is the whole business case in one line, and it's also where the risk sits, because Vault has a few rules every owner should know before staff start saving things.
If you want my team to walk through where an agent fits in your business, book a free SEO strategy session.
What Vault means for a business owner
Most admin work online starts with a login.
Reordering stock, downloading invoices, updating a listing, booking a courier: each one begins with a sign-in screen.
Vault is how Grok Bot gets past that screen for you.
According to the xAI Vault documentation, you save three things there: logins, cards and contact info.
The Bot can use a password or card to finish a task, but those values are filled into the web page directly and are never shown to it.
It can read your contact details, since it types those into delivery and billing forms.
For an owner, that split matters: your staff can ask a Bot to log in to the wholesaler without anyone sharing the password in a chat thread.
Which plans include Grok Bot
Vault is part of Grok Bot, so the first question is whether your subscription includes Grok Bot at all.
The X Subscription page for Grok Bot says it's included on the Premium, Super and Ultra plans.
The Plus plan doesn't include it.
The Vault page itself doesn't tie the feature to any one of those plans; what it does require is app version 0.75.2 or newer.
Use case: a local shop that reorders stock
Picture a hardware shop with three regular suppliers, each with its own trade portal.
The owner saves the three portal logins in Vault and adds a hint to each one, such as "Use for the timber supplier".
The shop address and delivery phone number go in as contact info.
Now a Bot can sign in to the right portal, fill the delivery details and get to the checkout page.
Whether it then pays on its own is a separate decision, covered in the payments section below.
Many owners will want the Bot to stop at the basket and send them a summary first.
Use case: a service firm with booking and invoice portals
A cleaning company or an accountancy practice lives in web portals: a booking tool, a payroll site, a bank's invoice download page.
Each of those logins can sit in Vault.
Where a portal uses single sign-on, a passkey or approval on another device, the Bot can't do that step alone.
It hands the computer to you: you choose Take over, finish that one step, then choose I'm done.
The signed-in session then stays on the Bot's computer, shared by all your Bots, so you don't repeat it every day.
When a portal emails a one-time code, the Bot can pick it up from a connected Gmail or Outlook inbox.
🔥 Want to see how small firms set up their first agent safely? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members comparing their setups. → Join the AI Profit Boardroom
Use case: an agency running Bots for a whole team
Agencies hit a different wall: several people, several clients, one set of tools.
Your personal Vault does not carry over to Team Bots.
A Team Bot keeps its own logins instead, added by an owner or manager under the Bot's accounts section.
Only managers can see or edit those logins, and the Bot can sign in with them for anyone on the team.
API keys for a Team Bot go under Secrets, as an environment variable name, a description and the value.
Every teammate who chats with that Bot uses the same secret, so the owner should only add keys the whole team is allowed to use.
That gives an agency a clean line: personal logins stay personal, and shared client tools live on the Team Bot.
What your staff can and can't see
| Item | Who manages it | Visible after saving? |
|---|---|---|
| Personal Vault login | The account owner | Password hidden |
| Personal Vault card | The account owner | Last four digits only |
| Team Bot login | Team Bot managers | Managers only |
| Team Bot secret | Team Bot owner or managers | Name and description only |
Saved values are write-only across the board.
Nobody, including you, can read an old password or key back out; you can only replace it.
That's useful when a staff member leaves: you replace the value and move on, with no copy sitting in a shared document.
The payment setting every owner should check
This is the biggest business risk in Vault, so read it twice.
Once a card is saved in Vault, it gets used at checkout with no prompt to you.
The docs say no setting requires approval for each use of a saved card.
If you want to sign off on every purchase, don't save the card.
Instead, enter it in the Secure Form when a Bot asks and leave "Securely save to Bot's vault" unticked, so it's used for that chat only.
On top of that, the approvals and privacy page lets you add an Ask first rule, such as "Ask first before paying for anything", which always stops a matching action.
For the full buying flow, see this site's Grok Bot shopping guide for business.
Wallets and the default payment method
Cards aren't the only way a Bot can pay.
Settings, Vault also has a Payment accounts list, where you can connect wallets such as Link, X Money or Shop Pay.
Below that sits a Default payment method, which is what Grok Bot tries first.
On a phone, the wallets live under Payments inside Settings, Vault; a connected one shows Connected and the account it's signed in to.
For a business, the useful part is the split between wallets and cards.
The docs say wallets such as Link or X Money need one order card per payment, so each purchase surfaces in the chat on its own.
With a Link account connected, a Bot can also ask you to approve a one-time card for a single purchase, showing the merchant, the items and the total.
You choose Pay, Pay another way or Deny, and nothing is charged if you decline or the request runs out.
That suits owners who want each spend visible without keeping a card on file.
Risks and limits to plan around
- Every Bot sees every item: Vault covers the whole account, and you can't restrict a login or card to one Bot.
- Chat details are kept: names, addresses and phone numbers given in chat are saved as contact info when the task ends. Tell the Bot when something shouldn't be kept.
- Phone limits: saved cards can't be edited on the phone yet, and to change a number you remove the card and add it back.
- Imports leave a file behind: a password manager export is unencrypted, so delete it after importing.
- Keys in files can disappear: Recover, Reset and updates can wipe secrets typed into files or tools on the Bot's computer. Keys stored properly are not affected.
Moving your logins over from a password manager
Most firms already keep logins in a password manager or a browser.
Grok Bot accepts a CSV export, on desktop only, from LastPass, Bitwarden, 1Password, Firefox, Chrome or Edge, or Safari and Apple Passwords.
The file is read locally and must be under 5 MB, duplicates are skipped, and rows without a password or with a non-https site are left out.
I'd only import the logins a Bot actually needs, not the whole company archive.
If you'd rather keep 1Password as the master copy, the computer and apps page explains how to connect it so each login is approved inside 1Password.
A one-week rollout plan
- Day 1: confirm your plan includes Grok Bot and update the app.
- Day 2: add Ask first rules for payments and new sign-ups.
- Day 3: save two or three logins for the most repetitive admin task, with hints.
- Day 4: save business contact info for deliveries and billing.
- Day 5: run one real task, such as downloading last month's supplier invoices.
- Day 6: decide whether a card belongs in Vault or stays in Secure Forms.
- Day 7: set up a Team Bot with its own logins if staff need shared access.
📞 Not sure which tasks to hand over first? Book a free SEO strategy session and my team will help you pick the admin jobs to start with. → Book your free call
Who should hold the keys in your business
Keep the account owner role small.
The person who owns the account controls the personal Vault, and every Bot on that account can use what's in it.
For a team, a Team Bot with a named manager is the tidier choice, since only managers can change its logins.
Write down who is allowed to add cards, and keep that list short.
Questions to answer before staff start saving things
- Who owns the account? Everything in the personal Vault is open to every Bot on it, so the owner should be the person accountable for spend.
- Which tasks need a login at all? Write the list of portals first, then save only those.
- Who approves payments? Name one person, and make sure the Ask first rule exists before any card is saved.
- Where do shared client tools live? On a Team Bot with a named manager, never in someone's personal Vault.
- Where is the master copy? Vault values can't be read back, so the original password stays in your main password manager.
Ten minutes on these five questions avoids most of the clean-up work later.
When to keep something out of Vault
Some values don't belong there at all.
A company-wide licence key used by setup scripts is stored by a team admin as a Team Secret on the Enterprise dashboard, which never reaches your Bots directly.
A card you only use once a year is easier to type into a Secure Form when needed.
And nothing sensitive should ever be pasted into a normal chat message, a Shell command or a file on the computer.
The AI Profit Boardroom has trainings on setting up agents for small teams, step by step.
Also On Our Network
- 🌐 The eight-step order I'd follow to fill Vault on a fresh account
- 🌐 An eight-row scorecard of Vault, from secret handling to saved-card payments
- 🌐 Five copy-paste prompts that make Vault the key cabinet of your Agent OS
- 🌐 Which GoldieBench models to pair with Vault for access maps and onboarding pages
FAQ: Grok Bot Vault For Small Business
Can my staff see the passwords saved in Grok Bot Vault?
No. Saved values are write-only: passwords stay hidden and cards show only their last four digits. Team Bot logins are visible to managers only.
Which plan do I need for Grok Bot Vault?
Grok Bot is included on the Premium, Super and Ultra plans, and Plus does not include it. Vault itself needs app version 0.75.2 or later.
Can a Team Bot use my personal Vault?
No. Team Bots cannot use your personal logins, cards or contact info. They keep their own logins and Secrets, managed by the Bot's managers.
How do I stop a Bot paying without me?
Don't save the card in Vault. Use a Secure Form with the save box unticked, and add an Ask first rule for payments.
📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉
🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉
About Julian
I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
- I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
- I've grown a YouTube channel to 400,000+ subscribers.
- I wrote "Link Building Mastery".
- My Udemy courses have taught over 29,000 students.
→ Get my best AI training inside the AI Profit Boardroom
Start small, set your payment rules first, and book a free SEO strategy session or join the AI Profit Boardroom to plan your Grok Bot Vault rollout.











