# Boreon™ · Agentforce Ohana & SI Force: 5 Agents, 25 Specialists

URL: https://boreon.com/agentforce
Language: en

> Boreon's Agentforce Ohana: five agents, 25 specialists and the SI Force, 13 helpers who handle every migration error live. People approve every change.

---
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.

[Book a working session](https://boreon.com/contact) [Meet the ohana](https://boreon.com/agentforce#team)

Salesforce is one of our closest partners.

Choose an agent to meet its team.

## 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.

1. [The ohana Five agents and twenty-five specialists, each specialist an Agentforce topic.](https://boreon.com/agentforce#team)
2. [The ohana way Five Hawaiian words for how the family works, one for each agent.](https://boreon.com/agentforce#ohana)
3. [Salesforce CRM and CRM Analytics moves Lightning and CRM Analytics dashboards into Tableau Next, with an agent at every step.](https://boreon.com/agentforce#crm)
4. [Say aloha Greet them and the whole ohana answers, each agent in its own voice.](https://boreon.com/agentforce#hello)
5. [One-click engage Put an agent to work in your org, or take it back out, in one click.](https://boreon.com/agentforce#engage)
6. [Grounded answers Every answer comes from the migration guide and the expertise each agent carries.](https://boreon.com/agentforce#grounded)
7. [They step in When an answer touches an agent's specialty, that agent offers to help.](https://boreon.com/agentforce#helps)
8. [People decide No agent starts or approves a migration. A signed-in person does.](https://boreon.com/agentforce#rules)
9. [Einstein Trust Layer Every AI call is grounded, masked, checked for toxicity and audited, with zero data retention.](https://boreon.com/agentforce#trust)
10. [Agentforce asks our layer When a question needs Tableau, Agentforce calls on the Boreon MCP Layer.](https://boreon.com/agentforce#together)
11. [An agent of your own An Agentforce agent that knows the platform, the migration guide and your data.](https://boreon.com/agentforce#your-agent)
12. [Tableau Next, grounded Tableau workbooks, and dashboards from Salesforce CRM and CRM Analytics, become Tableau Next dashboards once the grounding gate passes.](https://boreon.com/agentforce#tableau-next)

## 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.

Leilani Ohana Ambassador Kai Migration Architect Malia Semantic Layer Steward Koa Security & Trust Captain Nohea Multi-Modal Orchestrator

(Image: A coral octopus with a flower crown)

### 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 welcome in Agentforce

Also an expert in

- Tableau Cloud
- Tableau Server
- Moving between them

One click away

- Where are we connected?
- Meet the Agentforce Ohana

Their team

1. Welcome Guide Onboarding A tour of the Boreon MCP Layer, the rules that keep a migration safe, and where everything lives.
2. Agentforce Support Agent for Tableau Support Tableau Cloud and Tableau Server support: errors, limits, permissions, REST and publishing.
3. Migration Coach Guidance Walks a first migration: connect, plan, dry run, approve, verify.
4. Glossary Keeper Guidance Explains Tableau, Tableau Next, Data 360 and semantic-layer terms, each with an example from a migration.
5. Help Desk Liaison Support Gathers the facts a support case needs and hands off cleanly to a person.

Helpers in the SI Force

- Hōkū the Help Star Anything new

(Image: A dolphin navigator with a compass)

### 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 welcome in Agentforce

Also an expert in

- Tableau Next
- Moving between them
- Tableau Cloud
- Tableau Server

One click away

- Plan a workbook to Tableau Next
- What's on the source?

Their team

1. Inventory Scout Discovery Reads what's on a site: projects, workbooks, data sources, lineage and owners.
2. Grounding Analyst Tableau Next The grounding gate: which semantic model each data source converts on, field by field.
3. Viz Translator Tableau Next Translates each Tableau chart type into its Tableau Next form.
4. Dashboard Composer Tableau Next Dashboard layouts on Tableau Next's grid, faithful to the originals.
5. Dry-Run Rehearser Discovery Reads a dry run: what would be created, updated or skipped, and why.

Helpers in the SI Force

- Pua the Chart Mender Charts Tableau Next turns down
- Nalu the Version Wrangler API versions and shapes
- Iolani the Lens Reader CRM Analytics steps

(Image: An owl with reading glasses and a hibiscus)

### 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 welcome in Agentforce

Also an expert in

- Tableau Next
- Salesforce
- Moving between them

One click away

- Show the semantic layer
- What's in the CRM?

Their team

1. Data 360 Cartographer Data 360 Maps Data 360 objects, semantic models and their relationships.
2. Warehouse Liaison Warehouses Snowflake and Databricks: semantic views, metric views, catalogs and read-only roles.
3. Metric Contract Keeper Governance The define-once metrics each source publishes, and which one governs.
4. SQL Analyst Warehouses Explains read-only SQL over Data 360 and the warehouses, and what a result means.
5. Drift Watcher Governance Watches the layer for changes that wait for a person's approval.

Helpers in the SI Force

- Iwa the Stream Stitcher Data 360 streams
- Lani the Lake Lantern Data copied into Data 360
- Kalo the Model Gardener Semantic models
- Ola the Transform Weaver Data 360 transforms
- Ala the Path Finder Joins between objects

(Image: A Hawaiian monk seal with a leaf shield)

### 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 welcome in Agentforce

Also an expert in

- Salesforce
- Tableau Cloud
- Tableau Server

One click away

- Is anything paused or refused?
- Show the audit trail

Their team

1. Security Blue Team Defense Least privilege, the sign-in circuit breaker and sealed secrets.
2. Red Team Challenger Offense, advisory only Challenges a plan the way an attacker would: permissions, exposure, prompt injection. It describes the risk and the defense, never the exploit.
3. Access Auditor Governance Checks how permissions and sharing carry to the target: who gains or loses access, and why.
4. Secrets Guardian Defense The credential vault: embedded credentials, key pairs and one-time reveals. It never repeats a secret.
5. Compliance Recorder Governance The append-only audit trail, and the evidence a reviewer asks for.

Helpers in the SI Force

- Keoni the Key Keeper Sign-ins and sessions
- Pono the Permission Pal Who may read what

(Image: A honu, the Hawaiian sea turtle, with a plumeria lei)

### 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 welcome in Agentforce

Also an expert in

- Tableau Next
- Moving between them

One click away

- What's the status of the run?
- Summarize my last migration

Their team

1. Multi-Modal Orchestrator Orchestration Routes each request to the right teammate, across text, renders and data.
2. Fidelity Inspector Quality Before-and-after renders: does the migrated view look and read the same?
3. Run Watcher Operations Live run status: done, exists, skipped or failed, every failure in Tableau's or Salesforce's own words.
4. Incident Responder Operations When something fails: the cause, the next step, and whether to run it again.
5. Report Writer Quality A short executive summary of a migration that a leader can read in a minute.

Helpers in the SI Force

- Pōki the Tide Peeker Slow answers and hiccups
- Mele the Number Matcher The data check

## The SI Force. Every error goes to the agent who knows it.

SI is for Super Intelligence. While a migration runs, each problem goes straight to the Ohana agent who owns that kind of trouble, and the agent sends one of its helpers. The helper says what happened, what was already done, and what you need to do next.

- **A helper for every error we have met** All 351 errors from 113 real runs have a helper. Anything new goes to Hōkū the Help Star, in Salesforce's own words, never dropped.
- **Helpers explain. People decide.** A helper never starts, approves or widens a migration. A signed-in person still types the approval phrase.
- **A refused sign-in stops everything** Keoni the Key Keeper pauses every sign-in and gives you the steps. Never a retry, so your account is never frozen.
- **One card for each kind of problem** The first of each kind is explained and the rest are counted, so the board never floods.

Ask the Ohana about any of it in Agentforce. They answer on Salesforce's model, through the Einstein Trust Layer, from the same handbook.

SI Force · the Ohana on it

Migration run into Tableau Next

1. **Koa** sent **Keoni the Key Keeper** Stopped safely
  Salesforce refused a sign-in, so every sign-in is paused to protect your account from being frozen.
  One refusal is a hard stop, never a retry.
  **You:** Read Setup, Login History for the reason, fix it, then clear the pause and run again.
2. **Kai** sent **Pua the Chart Mender** Already handled
  Tableau Next turned down how this chart was described.
  Pua knows this refusal: the chart is rebuilt in the shape Tableau Next takes, each one proven first.
  **You:** Plan the dashboard again.
3. **Malia** sent **Lani the Lake Lantern** Needs you
  A copy of CRM Analytics data into Data 360 didn't finish.
  Lani counts what Data 360 holds: a copy that already has every row counts as loaded.
  **You:** Run the same plan again. The copy never doubles.
4. **Nohea** sent **Pōki the Tide Peeker** Corrected
  Salesforce took longer than the run waits to answer this save.
  Pōki checked Tableau Next and the change is there, so it is marked done.
5. **Leilani** sent **Hōkū the Help Star** Needs you
  Something happened that the Ohana hasn't met before.
  Hōkū kept Salesforce's exact words for the team.
  **You:** Ask Leilani. The team learns it and gives it a helper.

Illustration · sample data

## 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.

1. 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
2. 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
3. ʻ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
4. 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
5. 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.

1. 01
  ### ConnectLeilani · Ohana Ambassador
  Leilani checks where you're connected: your Salesforce org, with CRM migrations switched on by an administrator.
  Ask Where are we connected?
2. 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.
  Ask What's in the CRM?What's in CRM Analytics?Migrate the Sales Executive Dashboard
3. 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.
  Ask Show the semantic layer
4. 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.
  Ask Can we go live with the Sales Executive Dashboard?
5. 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.
  Ask What's the status of the run?

[What becomes what, chart by chart](https://boreon.com/mcp/tableau-next-migration#salesforce-crm)

## 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.

Boreon MCP Layer

Aloha Agentforce, how are you today?

1. **Leilani** Ohana 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
2. **Kai** Migration 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
3. **Malia** Semantic 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
4. **Koa** Security & 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
5. **Nohea** Multi-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

Illustration · sample data

## 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.

1. 01 Check with Salesforce A check-only deploy of the agent and its topics. Salesforce checks everything and saves nothing.
2. 02 Add it to your org The agent deploys into your org, each of its specialists one of its topics.
3. 03 Switch it on Its newest version becomes active, ready for your people.
4. 04 Give you access Your 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.

**Koa** Security & Trust Captain

Stowed Engaging Engaged

1. Check with Salesforce
2. Add it to your org
3. Switch it on
4. Give you access

Version 1 is active

Illustration · sample data

## 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.

1. ### Topics
  Its five specialists, how the platform works, and the expert topics of its field.
  - Leilani
  - Kai
  - Malia
  - Koa
  - Nohea
2. ### Actions
  Agentforce's knowledge action, reading our migration guide in a Data Library.
3. ### 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.

Boreon MCP Layer

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 trail

Agentforce is here to help. What shall we move today?

Illustration · sample data

## They answer. Your people decide.

Every agent on the team keeps the same promises, in every answer.

1. 01 A person approves
  No agent starts, approves or changes a migration. A signed-in person does, with the typed approval phrase.
2. 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.
3. 03 Honest about limits
  When the guide doesn't cover a question, they say so and point to the Tableau or Salesforce documentation.
4. 04 One attempt
  Engaging and disengaging each try once. A refused sign-in pauses everything until a person clears it.
5. 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.
6. 06 On the record
  Every engage and disengage is written to the audit trail, and the Compliance Recorder can point to the entry.

[Einstein Trust Layer](https://boreon.com/mcp/einstein-trust-layer)

## 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

1. Grounded
2. Masked
3. Zero data retention
4. Toxicity checked
5. 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.

Illustration · sample data

1. 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.
2. 02
  Personal data masked
  Names, email addresses and other personal details become placeholders before the prompt reaches a model.
3. 03
  The model keeps nothing
  Zero data retention: the model provider stores none of the prompt and none of the answer.
4. 04
  Toxicity checked
  Every answer is scored for toxicity on its way back, before anyone reads it.
5. 05
  Audited in Data 360
  The whole exchange is written to an audit trail in Data 360, so it can be reviewed later.

[Agentforce Agent](https://boreon.com/mcp/agentforce-agent)

## 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.

**Your people** In Salesforce, in natural language **Agentforce** Your agent, in your org **Boreon MCP Layer** Knows your Tableau

**Tableau** Server or Cloud, read through Tableau's own APIs **Tableau Next** Visualizations and dashboards, in Salesforce

[Agentforce Agent](https://boreon.com/mcp/agentforce-agent)

## 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?

[Agentforce Agent](https://boreon.com/mcp/agentforce-agent)

## Checked before it goes live.

Salesforce checks the agent before anything is saved, a person deploys it, and it never changes under your feet.

1. 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.
2. 02
  Deploy
  A person types the deploy phrase. Deploying works only after a validation has passed, and it switches on the latest version.
3. 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.

[Tableau Next Migration](https://boreon.com/mcp/tableau-next-migration)

## 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

1. Maps to the Sales semantic model
2. 12 of 12 fields are in the model
3. 48,210 real rows behind it

Tableau Next · Sales workspace

- Revenue by region Visualization
- Pipeline trend Visualization
- Top accounts Visualization
- Sales Overview Dashboard

Sharing carried over Manager Editor Viewer

Live, after a person approved it

Illustration · sample data

1. ### 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.
2. ### 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.
3. ### 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.

[Book a working session](https://boreon.com/contact) [See it live at ai.boreon.com](https://ai.boreon.com/)
