For Salesforce admins · Early access

A Headful
Cloud for
your CRM.

For you. And your agents.

Connect your Salesforce orgs. Create users, configure access, and review leads in your chat. Let your agent prepare the work, with your approval before a change is applied.

Production and sandboxes. One workspace. You hold the controls.

headful.cloud / setup
Headful Cloud ● Example QA Sandbox

SETUP

⌘ Overview
☁ Salesforce orgs
⬡ Sandboxes
◈ Permission sets
▤ Leads
↗ Agent access
My leadsRead-only
3IN THIS EXAMPLE
QASELECTED ORG
Three fictional leads in an example sandbox
NAMECOMPANYSTATUS
Maya ChenOrbit LabsWorking
Alex RiveraNova SystemsOpen
Sam OkaforAltitude Co.Open
YOUR FAVORITE CHAT

“Show me the leads in my QA sandbox.”

Headful Cloud
Your chosen org. A focused lead view.
ILLUSTRATIVE PREVIEW · FICTIONAL RECORDS
☁ Multiple Salesforce orgs⬡ Discover visible sandboxes◈ Skills + authenticated MCP✓ You approve the changes

YOUR ORGS. YOUR HEADSPACE.

Give your Salesforce orgs
a place in your chat.

Headful Cloud brings users, access setup, permission sets, and leads into a focused workspace beside your conversation or in your browser. Your agent works with the same saved workflows and the orgs you choose.

Your Salesforce orgs

ProductionYour primary Salesforce org
OAuth
QA sandboxConnected separately
OAuth
Developer sandboxConnected separately
OAuth
Headful CloudYour admin workspace
Org accessYou choose
User creation & accessYou confirm
Lead viewingRead-only
Permission changesYou approve

One authenticated MCP connection

Your favorite chat

“Review Lead access
in my QA sandbox.”
Read the org.
Prepare a review.

Connect an OAuth-compatible MCP host.

Example connection. Each org has its own Salesforce login and consent. Your agent sees only the orgs you approve for that connection.

Start with production.

Connect your primary org and discover its visible sandboxes. Sign in to each sandbox separately before you or your agent can use it.

Keep secrets out of chat.

Save your Salesforce application credentials in Setup. Headful Cloud stores them encrypted; the plugin carries no org tokens or client secrets.

Keep the final say.

Your agent can prepare a user draft or access change. You review the exact fields and permissions before choosing Create or Apply.

YOUR ORGS, IN THE CONVERSATION

See what a headful
conversation looks like.

Choose an org. Inspect a lead. Prepare a permission change. Follow a fictional session, then try the small controls inside it.

Simulated session · fictional Salesforce data
ChatGPTNew conversationHeadful Cloud
You

Show my production org and its sandboxes.

Headful CloudExample complete
  1. Find owner-approved orgslist_orgsRead
  2. Read visible production sandboxeslist_sandboxesRead

Northstar Production is connected. UAT is visible, but it needs its own Salesforce login and consent before I can use it.

Your Salesforce orgsFictional workspaceOrg picker
Northstar ProductionProduction · ConnectedApproved
UATSandbox · Visible from productionSeparate login

Sandbox discovery is limited by Salesforce privileges. A visible sandbox is not a connected org.

Illustrative host styling. Real plugin and App availability depends on your host and workspace.

Choose the right org. Completed fictional example.

A USEFUL HEAD FOR THE WORK AT HAND

Less clicking around.
More work with context.

Complete a focused form in chat, then continue the same saved task in the detailed Headful workspace. Your org, user, draft, and verified operations stay together.

Choose the right org.

Keep production and sandbox connections together. Switch orgs in Setup or use the focused org picker in a compatible chat.

Separate Salesforce consent for each org

Find your sandboxes.

Read the sandbox inventory visible from your production org. Connect each sandbox with an application configured for it.

Discovery does not grant sandbox access

Review leads in focus.

Search leads by name or company, sort a returned list, and inspect record details from an org you connected.

Unconverted leads · read-only

Create a user with context.

Complete a compact form with the org’s available profiles, licenses, and supported settings. Review the exact user fields before choosing Create.

User created. Access setup is pending.

Continue with access setup.

Open the same user and workflow in the detailed workspace. Inspect current assignments, choose compatible permission sets, and review additions or removals.

Verified operations remain saved

Make access easier to inspect.

Browse permission sets and their object and field access. Prepare changes to custom labels, descriptions, and supported permission flags.

Custom permission sets only for edits

Review before you apply.

See the current values beside the proposed values. Approve or reject the review; an approved change is checked again in Salesforce.

Agents prepare. You approve.

Choose your agent’s access.

Grant access to selected orgs and decide whether the agent can prepare reviews. Revoke its Headful Cloud connection from Setup.

Read and proposal access are separate

START WITH SOMETHING USEFUL

An admin’s day.
A little more headspace.

01

Get your sandbox bearings.

Ask which sandboxes are visible from production. Connect the QA org you need, then grant your agent access to that org.

“List the sandboxes visible from my production org.”
02

Review your leads.

Choose an org and browse its unconverted leads. Open a record to see its company, status, and available contact details.

“Show the leads in my QA sandbox.”
03

Prepare a precise access change.

Inspect a custom permission set, prepare the intended Lead or field access change, and review it before applying.

“Prepare Lead read access in our Sales Review permission set.”
04

Create a user, then set up access.

Review the new user’s fields in a compact App. After creation is verified, continue in the workspace to assign or remove permission sets.

“Create a user for Maya Chen in my UAT sandbox.”

FROM HEADLESS TO HEADFUL

Connect your orgs.
Give your agent a head.

Headful Cloud supplies the MCP. You bring a Salesforce OAuth application and choose who can use your orgs.

01

Make yourself at home.

Sign in with your invited email. Add your Salesforce OAuth application and authorize production, then connect the sandboxes you need.

02

Bring Headful into chat.

Follow your host’s setup guide. Add headful.cloud/mcp through OAuth, sign in, and choose which orgs the agent may access.

03

Keep your head in the game.

Complete a compact creation form, then continue access setup in the detailed workspace. Read leads and review exact permission changes with the same org and workflow context.

A SMALL PACKAGE. A USEFUL HEAD.

Headful, in your
favorite chat.

The Agent Plugin pairs the authenticated MCP connection with four focused skills: Salesforce admin, user creation and access, lead review, and permission-set review.

Download the package for a supported local plugin workflow, or connect the MCP directly through your chat host’s custom connector setup.

Invitation-only beta. Headful Cloud is not yet listed or approved in the ChatGPT plugin directory. Manual installation and App rendering depend on your host and workspace.

Headful Cloud

YOUR SALESFORCE ADMIN PLUGIN

Salesforce admin SKILL
User creation & access SKILL
Lead review SKILL
Permission-set review SKILL
headful.cloud/mcp OAUTH + MCP
Compact forms + detailed workspace APPS

Your org access comes from your account and consent. The download contains no credentials.

A FEW THINGS TO GET YOUR HEAD AROUND

Before your
first flight.

Know what connects, what your agent can do, and where you stay in control.

Read the full setup guide ↗
What is Headful Cloud?

Headful Cloud is a Salesforce admin workspace with an authenticated MCP and an Agent Plugin. Connect your orgs, create Salesforce users, continue their access setup, inspect permission sets, and review leads. Compact chat Apps and the detailed workspace share the same saved workflows.

Do I need to create a Salesforce MCP?

No. Headful Cloud supplies the MCP and Apps your agent uses. You configure a Salesforce OAuth application, save its client ID and secret in Headful Cloud Setup, and authorize each org through Salesforce.

Can I connect production and several sandboxes?

Yes. Start with production to discover the sandbox inventory visible to that Salesforce user. Each sandbox needs its own login and OAuth consent, using an application configured for it. You can also connect a sandbox manually.

Can my agent change Salesforce without me?

Agents can read records and, if you grant proposal access, prepare supported permission-set changes. Approval happens in Headful Cloud, where you review the exact before and after. Lead changes and general Salesforce writes are outside this initial scope.

Can I use this with ChatGPT or Claude?

Headful Cloud exposes an authenticated MCP for compatible hosts. Use your host’s custom MCP connection workflow and follow the setup guide for available plugin installation paths. The examples above simulate ChatGPT and Claude; native host acceptance and store approval are separate from this preview.

What happens to my Salesforce credentials?

Application secrets and connected-org tokens are stored encrypted on the server. They are not included in the plugin or returned to your agent. Salesforce permissions still determine what the connected user can read or change.

Can I remove an agent’s access?

Yes. Revoke its Headful Cloud connection from Agent Access in Setup. To give an agent access to an org you add later, connect the agent again and select that org during consent.

How do I get access?

Join the launch list below. The beta is invitation-only. You can inspect the setup guide and download the plugin package while you wait for your invitation.

HEADS UP. YOUR CLOUD IS GETTING READY.

A clearer head
for your next org.

Join the launch list for Salesforce admins.
We’ll email you when your invitation is ready.

Launch updates only. By joining, you agree to our privacy policy.