This panel is a map of the whole route, shown before you do any of it. Each step below says what it is, what you need ready, and where it happens — and "Show me how" walks you through it.
Read it like a map, not a to-do list: nobody does this in one sitting. Real setup happens in pieces, over time — some of it in Salesforce, some in this console, some on a command line. You don't have to do any of it now — this is what you'll need to learn.
- 1Get your invoke token
The console issues a token, and Salesforce shows that token on every call the guards make — it's how the console knows a call really comes from your org.
You need: Admin access to this console.
Where it happens: This console → Settings → Invoke token.
Show me how
- Open Settings → Invoke token.
- Click Rotate.
- Copy the token shown on screen — it's shown in full only at this moment. Copy it now and keep it somewhere safe — you'll paste it at step 3. If you lose it, rotate again to get a new one.
- 2Install the Fyver Interceptor package
The package puts the Apex guard classes into your Salesforce org — they're what ask this console for a decision before an agent acts.
You need: A Salesforce admin login.
Where it happens: The Salesforce AppExchange, then your org's Setup.
Show me how
- On the AppExchange, open the Fyver Interceptor listing and click Get It Now. Sign in with your Salesforce admin login, and pick the org to install into — a sandbox or Developer Edition org is a good first try.
- Choose Install for Admins Only, check the acknowledgement box, and click Install. It takes a few minutes, and you'll get an email when it finishes.
- Check it landed: Setup → Installed Packages — you should see a row for Fyver Interceptor.
- 3Create the credential
A Named Credential in Salesforce holds two things: your console's address, and the token from step 1. The guards use it to reach the console — the token is never typed into code.
You need: The token from step 1, and your console's address.
Where it happens: Salesforce Setup → Named Credentials.
Show me how
- Setup → Named Credentials → the External Credentials tab → New. Name it
Fyver_Interceptor_Credential— copy the name exactly, underscores included — choose Custom as the protocol, and Save. - On that credential, add a principal named
Fyver_Interceptor. On the principal's permission-set mapping (Fyver Interceptor Access), add an authentication parameter namedInvokeTokenand paste your token from step 1 as its value. - Back on the Named Credentials tab → New: name it
Fyver_Interceptor, choose the external credential you just made, and paste your console's address as the URL — the address only, nothing after it. - On that same form: Generate Authorization Header stays unchecked, and Allow Formulas in HTTP Header must be checked — that check is what lets Salesforce send the token with each call.
- Give yourself access: Setup → Permission Sets → Fyver Interceptor Access → Manage Assignments → add your own user.
Names must match exactly — copy them, never retype. The install runbook in your Fyver packet has every field, in order.
- Setup → Named Credentials → the External Credentials tab → New. Name it
- 4Give your agent its Fyver Config record
The record ties a Salesforce agent to its Fyver ID, so the policies you write land on the right agent.
You need: The agent's API name — for the built-in examples,
Account_ResearcherandRefund_Concierge.Where it happens: Salesforce Setup → Custom Metadata Types → Fyver Config. One honest shortcut: when you later deploy from this console, the console creates this record for you — doing it by hand is only for the manual route.
Show me how
- Setup → Custom Metadata Types → Fyver Config → Manage Records → New.
- Name the record with the agent's API name — underscores, no spaces:
Account_Researcher, not "Account Researcher". - Agent ID: paste the agent's Fyver ID from its card in this console (Agents & servers). Leave the Named Credential field blank — blank means "use the default" from step 3.
- Save, and repeat for each agent.
- 5Connect this console to your org
The console signs in to your org, so it can see your agents, flows, and tools — and so the deploy at step 6 knows where to go.
You need: A Salesforce admin sign-in for that org.
Where it happens: This console → Settings → Connections → Salesforce.
Show me how
- In Salesforce: Setup → External Client Apps → your Fyver app → OAuth Settings — copy the Consumer Key and Consumer Secret in full.
- In this console: Settings → Connections → Salesforce — paste both, Save, then Reconnect and finish the Salesforce sign-in in the popup, as an admin of that org.
- Read the status line: it should say connected and name this org. Signing into the wrong org is silent — always check the name.
- Then go to Agents & servers → the Salesforce server card → Sync catalog, so the console picks up the org's tools.
- 6Deploy the guardrail
From your agent's card, the console pushes the Apex guard — and any Flow guards you pick — into the environment you connected. The dialog names that environment and its address before you confirm, so you always know where it will land.
You need: Steps 1–5 done.
Where it happens: This console → Agents & servers → your agent → Deploy guardrail.
Show me how
- On the agent's card, click Deploy guardrail. Check what's selected and the environment named at the top, then confirm.
- Flow guards arrive as drafts — activate each one in Salesforce Setup → Flows.
- In Agentforce Builder, point the agent's actions at the guards instead of the original flows.
- Run a test call and watch it appear in the Interceptor stream — allowed, blocked, or held for a person, with the policy that decided it named next to it.
- 1Get your invoke token
The same console token as the Salesforce route — the instance shows it on every call the guard makes.
Where it happens: This console → Settings → Invoke token.
- 2Install the Fyver Interceptor app in your instance
The app carries the ServiceNow guard into your instance, so agent actions ask this console before they run.
Where it happens: The ServiceNow Store, then your instance.
- 3Point the app at this console
The app's settings in your instance hold this console's address and the token from step 1.
Where it happens: Your ServiceNow instance → the Fyver Interceptor app's settings.
- 4Connect this console to your instance
The console signs in to your instance, so it can see your agents and tools — and so the deploy knows where to go.
Where it happens: This console → Settings → Connections → ServiceNow.
- 5Deploy the guardrail
From your agent's card, the console pushes the ServiceNow guard into the instance you connected.
Where it happens: This console → Agents & servers → your agent → Deploy guardrail.