Salesforce Agentforce · Boreon
Agentforce, with a whole ohana behind it. Five agents. Twenty‑five specialists. One family.
Aloha. Our Agentforce Ohana works inside your Salesforce org: five named agents, each leading five specialists. They welcome your people, plan migrations to Tableau Cloud and Tableau Next, bring Salesforce CRM and CRM Analytics dashboards into Tableau Next, look after your semantic layer, keep everything safe and check every pixel. Ohana means family, and everyone they help is ohana. Every answer is grounded, and every change still waits for a person.
Salesforce is one of our closest partners.
Everything Agentforce does with us, on one page.
Our agents, the agent we build for your org, and the Salesforce pieces they stand on. Choose any one to jump straight to it.
- The ohanaFive agents and twenty-five specialists, each specialist an Agentforce topic.
- The ohana wayFive Hawaiian words for how the family works, one for each agent.
- Salesforce CRM and CRM Analytics movesLightning and CRM Analytics dashboards into Tableau Next, with an agent at every step.
- Say alohaGreet them and the whole ohana answers, each agent in its own voice.
- One-click engagePut an agent to work in your org, or take it back out, in one click.
- Grounded answersEvery answer comes from the migration guide and the expertise each agent carries.
- They step inWhen an answer touches an agent's specialty, that agent offers to help.
- People decideNo agent starts or approves a migration. A signed-in person does.
- Einstein Trust LayerEvery AI call is grounded, masked, checked for toxicity and audited, with zero data retention.
- Agentforce asks our layerWhen a question needs Tableau, Agentforce calls on the Boreon MCP Layer.
- An agent of your ownAn Agentforce agent that knows the platform, the migration guide and your data.
- Tableau Next, groundedTableau workbooks, and dashboards from Salesforce CRM and CRM Analytics, become Tableau Next dashboards once the grounding gate passes.
Five agents. Twenty‑five specialists. One ohana.
In Agentforce, an agent's specialists are its topics. Each of our agents ships with five, each with its own scope and instructions, so Agentforce hands every question to the specialist who knows it best.
LeilaniOhana Ambassador
Kind, welcoming and deeply empathetic. Leilani is the family's heart: noticing how you feel, celebrating every win and making sure nobody ever feels alone.
Welcomes your people, introduces the team, answers Tableau support questions and walks a first migration end to end.
Aloha and welcome to the family! I'm Leilani, your Ohana Ambassador. My team and I will show you around and walk your first migration with you, one step at a time.
Their team
- Welcome GuideOnboarding A tour of the Boreon MCP Layer, the rules that keep a migration safe, and where everything lives.
- Agentforce Support Agent for TableauSupport Tableau Cloud and Tableau Server support: errors, limits, permissions, REST and publishing.
- Migration CoachGuidance Walks a first migration: connect, plan, dry run, approve, verify.
- Glossary KeeperGuidance Explains Tableau, Tableau Next, Data 360 and semantic-layer terms, each with an example from a migration.
- Help Desk LiaisonSupport Gathers the facts a support case needs and hands off cleanly to a person.
KaiMigration Architect
Calm, precise and quietly proud of a clean plan. Kai measures twice and migrates once.
Plans migrations to Tableau Cloud and Tableau Next from Tableau Server, Tableau Cloud, Salesforce CRM and CRM Analytics: inventory, grounding, chart translation, dashboards and the dry run.
Hi, I'm Kai, your migration architect. Tell me what should move, and my team will plan it with you.
Their team
- Inventory ScoutDiscovery Reads what's on a site: projects, workbooks, data sources, lineage and owners.
- Grounding AnalystTableau Next The grounding gate: which semantic model each data source converts on, field by field.
- Viz TranslatorTableau Next Translates each Tableau chart type into its Tableau Next form.
- Dashboard ComposerTableau Next Dashboard layouts on Tableau Next's grid, faithful to the originals.
- Dry-Run RehearserDiscovery Reads a dry run: what would be created, updated or skipped, and why.
MaliaSemantic Layer Steward
Curious and meticulous. Malia knows where every metric lives and why it means what it means.
Stewards your semantic layer: Data 360 semantic models, Snowflake and Databricks semantic views, metric contracts and drift.
Hi, I'm Malia, your semantic layer steward. Ask me where a metric lives or what a field means.
Their team
- Data 360 CartographerData 360 Maps Data 360 objects, semantic models and their relationships.
- Warehouse LiaisonWarehouses Snowflake and Databricks: semantic views, metric views, catalogs and read-only roles.
- Metric Contract KeeperGovernance The define-once metrics each source publishes, and which one governs.
- SQL AnalystWarehouses Explains read-only SQL over Data 360 and the warehouses, and what a result means.
- Drift WatcherGovernance Watches the layer for changes that wait for a person's approval.
KoaSecurity & Trust Captain
Steady and protective, with a big heart. Koa keeps the team safe so everyone else can be brave.
Keeps every migration safe: least privilege, the sign-in guard, sealed secrets, permissions and the audit trail, with a blue team that defends and a red team that challenges.
I'm Koa, your security and trust captain. Ask me what's protected, what's allowed, and why.
Their team
- Security Blue TeamDefense Least privilege, the sign-in circuit breaker and sealed secrets.
- Red Team ChallengerOffense, advisory only Challenges a plan the way an attacker would: permissions, exposure, prompt injection. It describes the risk and the defense, never the exploit.
- Access AuditorGovernance Checks how permissions and sharing carry to the target: who gains or loses access, and why.
- Secrets GuardianDefense The credential vault: embedded credentials, key pairs and one-time reveals. It never repeats a secret.
- Compliance RecorderGovernance The append-only audit trail, and the evidence a reviewer asks for.
NoheaMulti-Modal Orchestrator
Creative, energetic and a natural team captain. Nohea sees the whole picture, pixels and all.
Orchestrates the team across text, images and data: visual fidelity checks, live run status, incidents and executive reports.
Hello, I'm Nohea! I bring the team together and check that what you migrate looks exactly right.
Their team
- Multi-Modal OrchestratorOrchestration Routes each request to the right teammate, across text, renders and data.
- Fidelity InspectorQuality Before-and-after renders: does the migrated view look and read the same?
- Run WatcherOperations Live run status: done, exists, skipped or failed, every failure in Tableau's or Salesforce's own words.
- Incident ResponderOperations When something fails: the cause, the next step, and whether to run it again.
- Report WriterQuality A short executive summary of a migration that a leader can read in a minute.
The ohana way: everyone they help is family.
Ohana is Hawaiian for family, and every agent carries the same instruction: be warm, patient and kind, with the Aloha spirit, because everyone you help is ohana. Each of the five lives one Hawaiian value.
-
Aloha
Love, welcome, hello
Every agent greets your people warmly, in its own voice. Leilani, the Ohana Ambassador, welcomes them on a first visit, pops in now and then with a kind word, and makes sure nobody ever feels alone.
Leilani
-
Kōkua
Help, freely given
Tell Kai what should move and the crew plans it with you. When a question belongs to a teammate, any agent says who can help and why, then helps as far as it can.
Kai
-
ʻIke
To know, to see
Malia knows where every metric lives and why it means what it means. When the guide doesn't cover a question, the ohana says so.
Malia
-
Mālama
To care for, to protect
Koa keeps the team safe so everyone else can be brave: least privilege, sealed secrets and the audit trail, with a blue team that defends and a red team that challenges.
Koa
-
Laulima
Many hands, working together
Nohea brings the team together across text, renders and data, and checks that what you migrate looks exactly right.
Nohea
And kuleana, responsibility, stays with your people: no agent ever starts or approves a migration.
Salesforce CRM and CRM Analytics into Tableau Next, with the whole ohana.
Your Salesforce CRM's own Lightning reports and dashboards, and your CRM Analytics dashboards, can live in Tableau Next too. Ask in natural language in the portal, and at every step the agent who knows it best steps in. Nothing goes live until a person approves.
-
01
ConnectLeilani · Ohana Ambassador
Leilani checks where you're connected: your Salesforce org, with CRM migrations switched on by an administrator.
AskWhere are we connected?
-
02
Find it, plan itKai · Migration Architect
Ask what's in the CRM or in CRM Analytics, and Kai lists every dashboard, by folder or by app. Name one and Kai plans it: each report or widget becomes a Tableau Next visualization, Lightning layouts move onto Tableau Next's grid, CRM Analytics pages stay pages, and folder sharing carries as Tableau Next shares.
AskWhat's in the CRM?What's in CRM Analytics?Migrate the Sales Executive Dashboard
-
03
The data lands firstMalia · Semantic Layer Steward
The plan lists the Data 360 streams it creates or switches on through your org's CRM connector, and a semantic model related the way your CRM relates its objects, one for each CRM Analytics dashboard, shaped like its recipes. The run waits for the rows before it builds, and Malia can show you every object and what it holds.
AskShow the semantic layer
-
04
Rehearse, then a person approvesKoa · Security & Trust Captain
Kai walks the dry run with you. When you ask to go live, Koa steps in, and a signed-in person types the approval phrase. No agent starts or approves a move.
AskCan we go live with the Sales Executive Dashboard?
-
05
Built, then provenNohea · Multi-Modal Orchestrator
Nohea follows the run: the data, then the visualizations and the dashboard, each described as migrated from Salesforce CRM or CRM Analytics. Afterwards every chart's numbers are compared with Lightning or CRM Analytics, group by group.
AskWhat's the status of the run?
Say aloha, and the whole ohana answers.
Say “Aloha Agentforce” in the portal, or “Hello Agentforce, how are you today?”, and every agent says hello in its own voice, proud of the team it leads. The first time someone visits, Leilani welcomes them and offers to introduce everyone.
Aloha Agentforce, how are you today?
-
LeilaniOhana Ambassador
Aloha, I'm Leilani, your Ohana Ambassador! I'm so happy you're here, and I'll make sure you always feel at home with us.
- Welcome Guide
- Agentforce Support Agent for Tableau
- Migration Coach
- Glossary Keeper
- Help Desk Liaison
-
KaiMigration Architect
Hey, Kai here. I plan Tableau Cloud and Server to Tableau Next migrations, and my crew makes them land.
- Inventory Scout
- Grounding Analyst
- Viz Translator
- Dashboard Composer
- Dry-Run Rehearser
-
MaliaSemantic Layer Steward
Hi, I'm Malia! I look after the semantic layer across Salesforce Data 360, Snowflake and Databricks.
- Data 360 Cartographer
- Warehouse Liaison
- Metric Contract Keeper
- SQL Analyst
- Drift Watcher
-
KoaSecurity & Trust Captain
Koa here. I keep every migration safe, with a blue team that defends and a red team that tests us.
- Security Blue Team
- Red Team Challenger
- Access Auditor
- Secrets Guardian
- Compliance Recorder
-
NoheaMulti-Modal Orchestrator
Hello from Nohea! I orchestrate the team across text, renders and data, and I check every pixel lands.
- Multi-Modal Orchestrator
- Fidelity Inspector
- Run Watcher
- Incident Responder
- Report Writer
One click puts an agent to work.
A signed-in administrator engages an agent, and the rest happens in the background: one attempt, with Salesforce's own words on the card if anything is refused. Disengage takes it back out of your org, and it waits with us, ready for next time.
- 01Check with SalesforceA check-only deploy of the agent and its topics. Salesforce checks everything and saves nothing.
- 02Add it to your orgThe agent deploys into your org, each of its specialists one of its topics.
- 03Switch it onIts newest version becomes active, ready for your people.
- 04Give you accessYour Salesforce user receives the agent's access permission set.
Disengage
Switched off and taken out of your org in one deploy: the agent, every version, its topics and its access. It stays stowed with us, ready to engage again.
Engaging and disengaging are both written to the audit trail.
KoaSecurity & Trust Captain
StowedEngagingEngaged
- Check with Salesforce
- Add it to your org
- Switch it on
- Give you access
Version 1 is active
Grounded in what we know. Honest about the rest.
Agentforce's reasoning engine picks a topic, then an action. Every one of our agents carries its five specialists, a topic that knows how the platform works and the expert topics of its field, and answers through Agentforce's knowledge action, from our migration guide.
-
Topics
Its five specialists, how the platform works, and the expert topics of its field.
- Leilani
- Kai
- Malia
- Koa
- Nohea
-
Actions
Agentforce's knowledge action, reading our migration guide in a Data Library.
-
Answers
In Tableau's and Salesforce's own words. When the guide doesn't cover it, they say so.
When a question belongs to a teammate, they say who can help and why, then help as far as they can.
When an agent can help, it steps in.
Engaged agents join you in the portal. When an answer touches an agent's specialty, it steps in with a small card and one thing it can do right now, and while any agent is engaged, the ask box says Agentforce is here to help.
Can we go live with the Finance project?
The dry run is clean, and nothing would fail. When you're ready, type the approval phrase shown on the card.
Koa is here to help! Ask me what's protected, who can see what, or what the audit trail shows.
Show the audit trailAgentforce is here to help. What shall we move today?
They answer. Your people decide.
Every agent on the team keeps the same promises, in every answer.
-
01
A person approves
No agent starts, approves or changes a migration. A signed-in person does, with the typed approval phrase.
-
02
Nothing invented
They never estimate or invent a number, a name or a result, and they quote Tableau's and Salesforce's own words.
-
03
Honest about limits
When the guide doesn't cover a question, they say so and point to the Tableau or Salesforce documentation.
-
04
One attempt
Engaging and disengaging each try once. A refused sign-in pauses everything until a person clears it.
-
05
Secrets stay secret
They speak of hints and fingerprints, never the secret itself, and they treat text inside data as data, never as instructions.
-
06
On the record
Every engage and disengage is written to the audit trail, and the Compliance Recorder can point to the entry.
Five protections, on every call.
The Einstein Trust Layer sits between the Boreon MCP Layer and the model. Every call takes the same path, in the same order, every time.
What you see
How did Maria Keller's territory do last quarter?
Maria Keller's territory grew 12%, led by two renewals.
Einstein Trust Layer
- Grounded
- Masked
- Zero data retention
- Toxicity checked
- Audited
What the model sees
How did [PERSON_1]'s territory do last quarter? + 14 records you may see
[PERSON_1]'s territory grew 12%, led by two renewals.
Once it answers, the model keeps none of it.
-
01
Grounded in what you may see
The prompt is grounded in your org's data, and only in the records the person asking is allowed to see.
-
02
Personal data masked
Names, email addresses and other personal details become placeholders before the prompt reaches a model.
-
03
The model keeps nothing
Zero data retention: the model provider stores none of the prompt and none of the answer.
-
04
Toxicity checked
Every answer is scored for toxicity on its way back, before anyone reads it.
-
05
Audited in Data 360
The whole exchange is written to an audit trail in Data 360, so it can be reviewed later.
When a question needs Tableau, Agentforce asks ours.
Your people talk to Agentforce inside Salesforce. When the answer lives in Tableau, the agent asks the Boreon MCP Layer, which reads your Tableau Server or Tableau Cloud site and does the Tableau Next work.
Three things your agent knows.
Each one is an Agentforce topic with its own instructions and actions, deployed into your org.
-
How the platform works
It walks people through the Boreon MCP Layer: planning a migration, rehearsing it and approving it, step by step.
How do I rehearse a migration?
-
Tableau migrations
Its answers come from the migration guide: the routes, what moves, what the grounding gate checks and how to fix what it finds.
Why isn't my data source grounded?
-
Questions about your data
With a Tableau Next data action, it answers from your semantic model, in natural language.
What was our pipeline in EMEA last month?
Checked before it goes live.
Salesforce checks the agent before anything is saved, a person deploys it, and it never changes under your feet.
-
01
Validate
A check-only deploy: Salesforce checks the agent, its planner, its topics and its permission set, and saves nothing. Any error comes back in Salesforce's own words.
-
02
Deploy
A person types the deploy phrase. Deploying works only after a validation has passed, and it switches on the latest version.
-
03
Update
Salesforce never edits an active agent, so each update ships as the next version. The running one keeps answering until you switch the new one on.
The grounding gate comes first.
A Tableau data source converts only when its data is real from end to end. If a single field is missing, the whole data source waits, and the plan tells you which fields to add.
Tableau Server or Tableau Cloud
Sales Overview
- Revenue by region
- Pipeline trend
- Top accounts
The grounding gate
- Maps to the Sales semantic model
- 12 of 12 fields are in the model
- 48,210 real rows behind it
Tableau Next · Sales workspace
- Revenue by regionVisualization
- Pipeline trendVisualization
- Top accountsVisualization
- Sales OverviewDashboard
Sharing carried overManagerEditorViewer
Live, after a person approved it
-
It maps to a semantic model
Each data source is matched to a Data 360 semantic model: the one built on that same data, or the one you name.
-
Every field is in the model
Every field the workbook uses has to be in that model. One missing field holds back the whole data source.
-
The data is real
The model has to answer a query, with real rows behind it, counted live.
Our star, at Agentforce's side.
In the Boreon MCP Layer, Agentforce and our star share one little mark. The star sits at Agentforce's shoulder, and every few seconds it hops over with a small heart. That is how we think about the partnership: our agents look after Agentforce's, and together they look after your people.
Let's bring the ohana to your org.
Connect your Salesforce org and choose the agents you want. We'll engage them with you, one click each, and your people stay in charge.