> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/account-intelligence/getting-started/salesforce/salesforce-iframe-installation.md).

# Salesforce iFrame Installation

> **Note:** To view journeys on your Salesforce dashboard, make sure you complete the integration with HockeyStack first

### Step 1: Modify permissions to allow installation

You can read how to modify permissions to allow installation in this doc: [Salesforce Permissions](/account-intelligence/getting-started/salesforce/salesforce-permissions.md)

### Step 2: Add sales reps as viewers in HockeyStack

Every sales rep who needs to see the iFrame in Salesforce must be added as a viewer in HockeyStack.

1. In HockeyStack, go to **Workspace Settings (under logo in sidebar) > Team**
2. Click **Invite** in **'Team Members'** section
3. Enter the rep's email and set their role to **Viewer**
4. Repeat for each rep who needs iFrame access

### Step 3: Click "Upload iFrame" in HockeyStack

1. Go to Atlas > Integrations
2. Click on Salesforce "Configure" button, in the CRM section
3. Click on "Upload iFrame"

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2FQB4L9eZLtWiE0xc6dSJD%2FScreenshot%202025-04-28%20at%208.09.41%E2%80%AFAM.png?alt=media&amp;token=c83ac219-f95b-490e-858d-82ba042c95f5" alt=""><figcaption></figcaption></figure>

### Step 4: Install HockeyStack components in Salesforce

When you click Upload iFrame, HockeyStack automatically deploys two components (HockeyStack and HockeyStack Full App) to your Salesforce org. You'll then need to manually add them to your views in Salesforce.

* **HockeyStack** — for embedding on **record pages** (Account, Contact, Lead). Shows account intelligence or contact/lead timelines contextually based on the record you're viewing.
* **HockeyStack Full App** — for adding HockeyStack as a **standalone tab or full page**. Loads the complete HockeyStack dashboard inside Salesforce.

**To add HockeyStack to a record page (e.g. Account):**

1. In Salesforce, Settings → Advanced Setup → Lightning App Builder
2. Edit a record page (Account, Contact, or Lead)
3. In Custom Components, find `HockeyStack` , then drag and drop it to the desired location on your page.
4. Click Save, then Activate the page if prompted.

**To add HockeyStack as a standalone tab:**

*To add as a full app page:*

1. In Salesforce, Settings → Advanced Setup → Lightning App Builder
2. Edit or create an App Page or Home Page
3. You'll see both `HockeyStack` and `HockeyStack Full App` in Custom Components

*To add as a tab:*

1. Setting → Setup → Tabs → Lightning Component Tabs
2. Find `hockeystackFullApp` — label is "HockeyStack Full App"
3. Note: Upload iFrame only makes this tab-capable, you still need to manually create and add the tab in Salesforce for reps to see it."

⚠️Note: Reps must have HockeyStack licenses to access the Full App. This is different from the account record iframe, where reps can view without a license.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hockeystack.com/account-intelligence/getting-started/salesforce/salesforce-iframe-installation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.