Design preview · in development
The admin agent that shows its work.
HB Admin plans each Salesforce change, waits for your approval, runs it and checks the result. Then it drafts the Jira update in your own words.
See all screensOpen the prototype
HB Admin is not available yet. This site shows the design and a clickable prototype. Desktop app for macOS and Windows.
Fixed - Anna and the other Sales users have read access on Discount now.1
Reason was the Sales_Core permission set - no read access on the field.2
3Also moved Discount to the Pricing section on the layout3 and updated the help text - max 20 % without manager approval.4
4Deployed to Production today 09:23 confirm5 and checked with Anna's user - read access is there.6
Open point: Tom asked about a discount reason field7 - I would say separate ticket.
Plan, approve, run, proof
Every change goes through the same four steps. Reads skip the approval.
1Plan
You ask in plain words. HB Admin reads the org and shows the steps, a visual diff and the way back. Every number says if it is measured, estimated or unknown. P3 · Plan
fls.set(Sales_Core, Opportunity.Discount__c, read=true)layout.moveField(Opportunity-Northwind Sales Layout, Discount__c, Other → Pricing)field.setHelpText(Opportunity.Discount__c, "Approved discount in percent. Max 20 % without manager approval.")Approved discount in percent. Max 20 % without manager approval.
| What | Value | Source |
|---|---|---|
| Users who get Read | 74 | Measured |
| Profiles using the layout | 3 - assignments unchanged | Measured |
| Deploy time | about 2 min (UAT 1 min 48 s) | Estimated |
| Flows / integrations that react | — | Unknown |
2Approve
Only you approve, never the model. A small change takes one click. A broad change asks you to type the org name. P4 · Approval
3Run
The run shows the deploy ID and a Stop button at all times. If the scope changes during the run, it stops. P5 · Run
4Proof
HB Admin reads the result back from the org, saves a receipt and keeps the way back ready. P7 · Receipt
- Deploy
- 0Af5g00000Q3dPL succeeded 3/3 - no tests (no Apex)
- Check
- Anna Read on Discount__c = true · 09:24:10 Measured
- Approved
- Alex Novak 09:21:02 - typed name and class
- Assistant saw
- 3Component names and counts - no record values
- Way back
- Snapshot S-0142-prod from 09:21:10
What HB Admin does for you
Diffs that look like Setup
Before and after, drawn like the Setup page you know: page layouts, field access, picklist values. Added, removed and changed items are marked in colour and in words.
Jira updates in your voice
HB Admin drafts the comment from the proof, the way you write. Every claim links to its evidence. Nothing is posted until you send it.
Local Git history
Every snapshot and every change is a commit in a local repository. You see what changed, why, and who approved it. No GitHub account needed.
Logins stay on your computer
Org logins live in the macOS Keychain or the Windows Credential Manager. Per client, you choose what the AI model may see.
One workspace per client
Orgs, Jira site, repository and language stay with their client. Evidence from one client never goes to another client’s Jira.
Your own AI agent
HB Admin works with the Claude Code or Codex you already use, with your own paid plan. The Salesforce CLI and Git come with the app.
Later: compare as a user
See the page a user really gets in two orgs, side by side, and why it differs. Planned for v1.5. C1 · Compare as a user
All the screens
The full design has 34 screens. The main ones follow one fictional story: Alex gives Anna access to a field, from the first question to the Jira comment.
Where we are
- HB Admin is in design. There is no download yet.
- The screens are design mockups. All companies, people and data in them are fictional.
- Version 1 will only make changes that have an exact way back. Features and dates can still change.
Early access
We are looking for Salesforce admins and consultants who want to test the first builds and tell us what is missing.