> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/backup-and-archive/backup-and-archive-in-salesforce/installing-or-upgrading-the-salesforce-package.md).

# Installing or Upgrading The Salesforce Package

## Overview

When you connect a Salesforce org to your Flosum Cloud Apps tenant, the Backup & Archive Salesforce package is installed in that org. Once the app is installed, you can upgrade it through your Backup & Archive settings. If you have trouble installing or upgrading the package, you can do so directly by following the instructions in this article.

{% hint style="info" %}

#### Recommended Upgrade Process

The recommended process for upgrading the Backup & Archive Salesforce package is explained in the following article. Use the instructions on this page only if you have trouble with that process.

* [Changing Integrations Settings](/backup-and-archive/settings/organization-settings/backup-and-archive-settings-integrations.md)
  {% endhint %}

## Installing or Upgrading Backup & Archive Package

{% stepper %}
{% step %}

### Package Installation URL

**Salesforce Domain URL**

To get the **Package Installation** URL for your Salesforce org, you must first get your org's **Salesforce Domain** URL.

1. Log in to the Salesforce org where you want to install the Flosum Backup & Archive package.
2. Copy the org's domain URL from the browser's address bar. 

   <figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2FcCuSq4DXoe7gulOWeDpq%2FInstallingBackupArchivePackage-S01-01.png?alt=media&amp;token=b095b10a-7607-48db-b36f-0e850913f860" alt=""><figcaption></figcaption></figure>

**Package Path**

Each version of the package has its own path; always select the current path unless you have a specific reason for selecting the previous version.

{% hint style="warning" %}
Flosum rolls out new versions region by region, so different tenants receive them at different times. If you install a package from a newly released version, your tenant's region may not have received that release yet, which can produce unexpected results. If you are unsure which version to install, check with Flosum's Customer Support team.
{% endhint %}

<table><thead><tr><th width="120.33331298828125">Version</th><th width="130.3333740234375">Release Date</th><th>Path</th></tr></thead><tbody><tr><td>2.5 (current)</td><td>2026-09-29</td><td><code>/packaging/installPackage.apexp?p0=04tgK000000NiGTQA0</code></td></tr><tr><td>2.2</td><td>2026-07-09</td><td><code>/packaging/installPackage.apexp?p0=04tgK000000E0OLQA0</code></td></tr><tr><td>2.1</td><td></td><td><code>/packaging/installPackage.apexp?p0=04tgK000000E04zQAC</code></td></tr></tbody></table>

**Complete Package Installation URL**

Combine your **Salesforce Domain URL** and the **Package Path** for the version you wish to install to create the complete **Package Installation** **URL**. See the format below.

```
https://<Salesforce Domain URL><Package Path>
```

1. Replace `<Salesforce Domain URL>` with your org's **Salesforce Domain** **URL** you found earlier in this guide.&#x20;
2. Replace the `<Package Path>` with the **Path** from the table above. Enter the path exactly as shown, preserving its capitalization.

{% hint style="info" %}

#### Example

The URL below is for reference only. Use your own Salesforce **My Domain** **URL**, followed by the exact, case-sensitive **Package Path**.

{% code overflow="wrap" %}

```
https://orgfarm-3c51b5bc70-dev-ed.develop.lightning.force.com/packaging/installPackage.apexp?p0=04tgK000000NiGTQA0
```

{% endcode %}
{% endhint %}

**Enter Package Installation URL**

1. Paste the **Package Installation** **URL** in a new browser tab.
2. The **Install/Upgrade Package** page will load.
   {% endstep %}

{% step %}

### Install/Upgrade Package

Installing and upgrading the Backup & Archive Salesforce package follow nearly the same process. Each is explained separately below.

**Install**

1. Choose who you want to install the package for.
2. Expand the **Advanced Options**.
3. For the **Apex Compile** option, select **Compile only the Apex in the package**.
4. Click **Install**.&#x20;

   <div align="left"><figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2FG9Bt0fhOVJDUitcYWbUj%2FInstallingBackupArchivePackage-S01-01.png?alt=media&amp;token=e1e72ec6-19a2-43b5-9cf7-a0319b4c420c" alt="" width="563"><figcaption></figcaption></figure></div>

**Upgrade**

1. Choose who you want to install the package for.
2. Expand the **Advanced Options**.
3. For the **Apex Compile** option, select **Compile only the Apex in the package**.
4. For the **Package Upgrade Mode**, select **Mixed mode** (unless you specifically need to select one of the other modes).
5. Click **Upgrade**.&#x20;

   <div align="left"><figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2FFBFpZUaVg3CRIpugxV8L%2FInstallingBackupArchivePackage-S01-02.png?alt=media&amp;token=3be0d41f-0874-40d6-a34c-b091ababf0d4" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Complete Installation

The installation typically completes in 2 to 5 minutes.

1. Wait for the **Installation Complete** message.
2. Click **Done**.&#x20;

   <div align="left"><figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F2mLix6PnfkJd98caXIX8%2FInstallingBackupArchivePackage-S02-01.png?alt=media&amp;token=7c0f0546-add5-40e7-b91c-c8f4b6f82933" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Enable Access

This step depends on whether you installed or upgraded the package. Follow the section below that matches your scenario.

**Install**

After installing the package, you must enable access to your Backup & Archive tenant by adding a Connected App in Flosum's Global Settings. For instructions on completing this process, see the following article.

* [Enable Access to Flosum Backup & Archive Data](/global-settings/security/connected-apps/enable-access-to-flosum-backup-and-archive-data.md)

**Upgrade**

After upgrading a package that was previously connected to your Backup & Archive tenant through a Connected App, you only need to update the connection token by following the instructions in the article below.

{% hint style="info" %}
If you don't have a Connected App in Global Settings for this Salesforce package or you are upgrading from a pre-version 2.0 package, you must add a Connected App by following the instructions in the **Install** section above.
{% endhint %}

* [Updating Backup & Archive Salesforce Package Token](/backup-and-archive/backup-and-archive-in-salesforce/updating-backup-and-archive-salesforce-package-token.md)
  {% endstep %}
  {% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flosum.com/backup-and-archive/backup-and-archive-in-salesforce/installing-or-upgrading-the-salesforce-package.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.