# Installation

{% hint style="info" %}
If you need tailored guidance for your Salesforce configuration, [contact our team](mailto:support@birdie.so).
{% endhint %}

{% hint style="warning" %}
We recommend installing and configuring the Salesforce package using a dedicated system account rather than a personal user account.

This ensures that actions like posting recordings are not tied to an individual user, which improves consistency, avoids issues when someone leaves the company, and keeps ownership clear.
{% endhint %}

### Step 1: Install the Birdie App

1. Open the Birdie listing on the Salesforce AppExchange:\
   👉 [Birdie on Salesforce AppExchange](https://appexchange.salesforce.com/appxListingDetail?listingId=b0108d43-09fe-4101-85b5-096c5c88c3d2)
2. Click **Get It Now** and install the app into your Salesforce org.

   * When prompted, select **Install for All Users**.

### Step 2: Salesforce IP Allowlisting

Salesforce security requires you to allow Birdie’s servers IPs into your org.

#### How to whitelist Birdie IPs

1. Go to **Setup** in Salesforce
2. Search for **Network Access**
3. Click **New** and add: \
   `Start IP Address:`` `<mark style="color:$warning;">`3.20.198.186`</mark>\
   `End IP Address:`` `<mark style="color:$warning;">`3.20.198.186`</mark>\
   `Description:`` `<mark style="color:$warning;">`Birdie ip 1`</mark>
4. Save
5. Same for our second ip, click New and add:\
   `Start IP Address:`` `<mark style="color:$warning;">`18.189.92.93`</mark>\
   `End IP Address:`` `<mark style="color:$warning;">`18.189.92.93`</mark>\
   `Description:`` `<mark style="color:$warning;">`Birdie ip 2`</mark>
6. Save

### Step 3: Add Birdie to the Case Page

1. In Salesforce, go to **Setup** → **Object Manager** → **Case**.
2. Select **Lightning Record Pages** and edit the layout you use.
3. Drag and drop the **Birdie Lightning Web Component (LWC)** onto the Case page.
4. Save and activate the updated layout.

Now the Birdie component will be visible on every Case.

<figure><img src="/files/pjI5QVaFWg97EV7oXADM" alt=""><figcaption></figcaption></figure>

### Step 4: Connect Birdie app for Salesforce to Your Birdie Workspace

1. Open any **Case** in Salesforce.
2. Find the Birdie component on the page.
3. Click **Connect to Birdie**.
4. Log in to your Birdie workspace and authorize the connection.

Your Salesforce org is now linked to Birdie.

<figure><img src="/files/7UmwMCBhKi6xfeO3Unw4" alt=""><figcaption></figcaption></figure>

### Step 5: Choose How Recordings Appear in Cases

In your Birdie workspace, go to [**Settings** **→ Integrations → Salesforce**.](https://app.birdie.so/settings/helpdesk)\
\
Here, you can decide how new screen recordings will be posted into Cases.

You have three options:

1. **Private Post**
   * The recording appears as a private post in the Case.
   * The “author” will display as the Salesforce account used to install the Birdie app.
2. **Public Post**
   * The recording appears as a public post in the Case (visible to all with access).
   * The “author” will display as the Salesforce account used to install the Birdie app.
3. **New Email**
   * Birdie creates a new email on the Case thread with customizable details:
     * **Subject**
     * **Sender name**
     * **Sender email**

<figure><img src="/files/sBqZ4GcGWQi21kVOn7UY" alt=""><figcaption></figcaption></figure>

### Next Steps

Once setup is complete, your support agents can start requesting and receiving Birdie screen recordings directly inside Salesforce Cases. \
\
You can now also add Birdie in other flows on Salesforce.


---

# Agent Instructions: 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:

```
GET https://docs.birdie.so/birdie-docs/helpdesk/salesforce-service-cloud/installation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.