> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/getting-started/signing-up-with-arm/autorabit-arm-app-installation-and-configuration-guide.md).

# AutoRABIT ARM - App Installation and Configuration Guide

Salesforce UI Compatibility Notice

The AutoRABIT package is a Second-Generation Managed Package (2GP) designed for Salesforce administrators to perform a one-time setup operation. It is supported exclusively in Salesforce Lightning Experience and is not compatible with Salesforce Classic.

Please ensure that your Salesforce org is using Lightning Experience before proceeding with the AutoRABIT package installation and configuration. Customers using Salesforce Classic must switch to Lightning Experience to complete the setup, as supporting Salesforce Classic is not technically feasible for this 2GP package.

{% hint style="info" %}
**PURPOSE:** This guide walks administrators through installing the AutoRABIT Salesforce package,\
configuring the Salesforce OAuth settings required by the connector, authorizing inbound and outbound connections, enabling licensed products, assigning the AutoRABIT ARM permission set, and completing product-side Salesforce org registration for ARM.
{% endhint %}

## Process at a Glance

<table><thead><tr><th valign="top">1 Install</th><th valign="top">2 Configure Salesforce</th><th valign="top">3 Authorize Connector</th><th valign="top">4 Register Org</th></tr></thead><tbody><tr><td valign="top">AppExchange / AgentExchange</td><td valign="top">OAuth &#x26; External Client App</td><td valign="top">Inbound + outbound</td><td valign="top">Product visibility + permissions</td></tr></tbody></table>

## 1. Before You Begin

Confirm the target Salesforce environment and the user accounts that will be used before starting the installation. This avoids installing into the wrong org or authorizing the connector with an unintended user.

* Choose the installation target: Production/Developer Org or Sandbox.
* Use a Salesforce account with sufficient access to install the package and update Setup settings.
* Identify the Salesforce user that will act as the AutoRABIT integration user.
* Before inbound authorization, make sure the integration user has the AutoRABIT Setup User permission set.
* Confirm that the customer has a valid ARM license enabled.

{% hint style="warning" %}
ENVIRONMENT CHOICE: The AppExchange flow is different for Production/Developer organizations and Sandboxes. Follow only the path that matches the org you are configuring.
{% endhint %}

## 2. Locate the AutoRABIT Package

#### 1. Open Salesforce AppExchange / AgentExchange

Open the Salesforce marketplace in a browser. Sign in if prompted.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FCf3aoeYzggm0n7KMaFMK%2Fimage.png?alt=media&amp;token=599a93c9-8730-44da-8fcb-1b727dbfef0f" alt=""><figcaption><p><em>Figure 1. Salesforce AppExchange / AgentExchange landing page</em></p></figcaption></figure>

#### 2. Search for AutoRABIT

Use the marketplace search field and search for “AutoRABIT.”

<br>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FUoP2wSpBNEQPUlYKjop6%2Fimage.png?alt=media&amp;token=8af978db-f193-4d72-9374-3e37c2b072b4" alt=""><figcaption><p align="center"><em>Figure 2. Searching the marketplace for AutoRABIT.</em></p></figcaption></figure>

#### 3. Open the AutoRABIT listing

Select the AutoRABIT Salesforce DevOps Platform listing from the search results.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FeokyUAlqmHdXJCRJq3rc%2Fimage.png?alt=media&amp;token=4071b34a-d40d-4455-b84f-33869275dd44" alt=""><figcaption><p align="center"><em>Figure 3. AutoRABIT listing in the marketplace search results.</em></p></figcaption></figure>

## 3. Install in a Production or Developer Org

#### 1. Select Get It Now

From the AutoRABIT listing, choose “Get It Now” to begin the production/developer installation flow.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FIRDHvpKk4UhGlh9YSaCe%2Fimage.png?alt=media&amp;token=90597765-b91f-49fe-b1cd-f1f49dec1ff7" alt=""><figcaption><p><em>Figure 4. “Get It Now” on the AutoRABIT listing.</em></p></figcaption></figure>

#### 2. Authenticate to Salesforce

Log in with the Salesforce credentials associated with the target Production/Developer org.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FdlKRYNI5CqNTqCbSNrZd%2Fimage.png?alt=media&amp;token=b8dc30ac-4dd4-4140-8a59-a46c5fb7f745" alt=""><figcaption><p>Figure 5. Salesforce sign-in prompt launched from the marketplace.</p></figcaption></figure>

#### 3. Use the correct Salesforce or business identity

If Salesforce requests account identification, use the Salesforce or business email tied to the intended org.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FuyN9lrfTzjZbJx1UrtW8%2Fimage.png?alt=media&amp;token=bd62337d-a0aa-43eb-a9c5-312348b597d3" alt=""><figcaption><p><em>Figure 6. Salesforce account identification screen.</em></p></figcaption></figure>

#### 4. Select the target org

Choose the Production/Developer organization where the package should be installed. Verify the org before proceeding.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FZssXbNVnMy8alH350KRL%2Fimage.png?alt=media&amp;token=62ff5bc0-4679-48e3-918f-68fb78a55fdd" alt=""><figcaption><p><em>Figure 7. Selecting the Production/Developer organization</em></p></figcaption></figure>

#### 5. Accept the marketplace terms and confirm installation

Review the installation details, accept the Salesforce AppExchange terms and conditions, and select “Confirm and Install.” Salesforce then redirects you to the package installation page in the selected org.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F38PLbfh3O9r94qcFqQJL%2Fimage.png?alt=media&amp;token=91dc9fa6-225b-42f8-9bbf-b0679987769c" alt=""><figcaption><p align="center"><em>Figure 8. Confirm Installation Details and “Confirm and Install.”</em></p></figcaption></figure>

## 4. Install in a Sandbox

#### 1. Select Try It

For a Sandbox installation, use the “Try It” option on the AutoRABIT listing instead of “Get It Now.”

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FIUX3vTKqUC6XwgVxMo1q%2Fimage.png?alt=media&amp;token=4ccb3292-d7f3-4588-9724-210a278a03a9" alt=""><figcaption><p>Figure 9. “Try It” option for the Sandbox installation path.</p></figcaption></figure>

#### 2. Continue to installation

On the trial setup page, confirm the information shown and select “Continue to Installation.”

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FdkMBjROJfe8i2imOpGVV%2Fimage.png?alt=media&amp;token=bb08096e-d7bd-4638-8a54-bc9ddb445540" alt=""><figcaption><p>Figure 10. Sandbox trial setup and “Continue to Installation.”</p></figcaption></figure>

#### 3. Log in and install

Select “Log In & Install,” then authenticate to the Sandbox in which the package will be installed.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FfISSwnh3Gkwn6UmuJr8z%2Fimage.png?alt=media&amp;token=91f73d1f-0529-4a76-b943-571e550b2971" alt=""><figcaption><p>Figure 11. “Log In &#x26; Install” for the Sandbox installation.</p></figcaption></figure>

#### 4. Install for Admins Only

When the Salesforce package installation screen opens, select “Install for Admins Only,” then click “Install.” This is the installation scope shown in the source procedure.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FdjlmcWW7NLpddldgiIVe%2Fimage.png?alt=media&amp;token=39f251e7-b456-4eb2-b96d-311a39df5732" alt=""><figcaption><p>Figure 12. Package installation scope set to “Install for Admins Only.”</p></figcaption></figure>

#### 5. Approve required third-party access

Salesforce may request approval for access to login.salesforce.com and test.salesforce.com. Select the option to grant access to these third-party sites, then click “Continue.”

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F6odU6PcPO51bASofe7Vu%2Fimage.png?alt=media&amp;token=6f5103e7-eb27-4399-abfe-3e83d1a1af4a" alt=""><figcaption><p>Figure 13. Approve Third-Party Access prompt.</p></figcaption></figure>

{% hint style="info" %}
**WHY THIS IS REQUIRED** The package requires these Salesforce endpoints so the AutoRABIT applications can complete the authentication and connectivity flow shown in this procedure.
{% endhint %}

#### 6. Wait for package installation to complete

Do not begin post-install configuration until Salesforce confirms the package has finished installing.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FYjeq5LeoUFewvexb8qGB%2Fimage.png?alt=media&amp;token=78e64d01-d342-44da-8d05-ea5aa8486516" alt=""><figcaption><p>Figure 14. Salesforce package installation in progress.</p></figcaption></figure>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FFlB2yVaD8R1mKKJj9mEX%2Fimage.png?alt=media&amp;token=e4209a55-ffce-4aea-bf86-53480ae85380" alt=""><figcaption><p>Figure 15. Salesforce may send an email if the package installation takes longer than expected.</p></figcaption></figure>

{% hint style="warning" %}
**LONG-RUNNING INSTALLATION** If Salesforce reports that the package is taking a long time to install, wait for either the completion screen or the Salesforce completion email before continuing.
{% endhint %}

## 5. Configure Salesforce OAuth and External Client App Settings

After the package is installed, configure the Salesforce OAuth settings required by the AutoRABIT Connector.

#### 1. Open OAuth and OpenID Connect Settings

In Salesforce Setup, search for and open “OAuth and OpenID Connect Settings.”

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fz3KMmtLOHuaiKsZ1J4Gm%2Fimage.png?alt=media&amp;token=47d18361-cef5-426c-8f8e-22e909487c30" alt=""><figcaption><p><em>Figure 16. Salesforce Setup navigation to OAuth and OpenID Connect Settings.</em></p></figcaption></figure>

#### 2. Enable the required OAuth settings

Verify that both of the following settings are enabled. If either is disabled, enable it:

* Allow Authorization Code and Credentials Flows
* Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FOP9aR7GImIfJ4IVTYybB%2Fimage.png?alt=media&amp;token=54e4b546-a308-462f-bf3a-58e54bfa3ad7" alt=""><figcaption><p><em>Figure 17. Required OAuth settings in Salesforce Setup.</em></p></figcaption></figure>

#### 3. Confirm the Salesforce warning

When Salesforce displays a warning about changing the setting, review it and click “OK” to continue.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F5RsBBylHcufqOQPbwAXT%2Fimage.png?alt=media&amp;token=6f832c1c-792a-4f94-b12c-8b0293d7be0a" alt=""><figcaption><p><em>Figure 18. Salesforce confirmation dialog when changing OAuth settings.</em></p></figcaption></figure>

#### 4. Confirm Session Settings

In Setup, search for and open “Session Settings.” Under “Session Settings,” make sure both of the following are disabled in the org:

* Lock sessions to the IP address from which they originated
* Lock sessions to the domain in which they were first used

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FiSa20ucWixvdYOoXybNw%2Fimage.png?alt=media&amp;token=dfdfbd3d-9fd3-4b52-b4fe-b7c6b1af7555" alt=""><figcaption></figcaption></figure>

#### 5. Open External Client App Manager

From Setup, open “External Client App Manager.”

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F40iuki95qsBTLwFyyKVN%2Fimage.png?alt=media&amp;token=e8e4ab83-6f30-4ced-a3bc-e065cfaeb4de" alt=""><figcaption><p><em>Figure 20. External Client App Manager in Salesforce Setup.</em></p></figcaption></figure>

#### 6. Open AutoRABIT Connector

Select only the external client app named “AutoRABIT Connector.” Do not select “AutoRABIT Connector (Dev).” The (Dev) External Client App (ECA) is reserved for debugging and troubleshooting purposes and must not be used for the standard AutoRABIT installation and configuration process.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FCi8g2Zp61FZf4op6sZh0%2Fimage.png?alt=media&amp;token=ba853c6f-4884-4061-a3a1-86bcc2b2afd6" alt=""><figcaption><p><em>Figure 21. Select the standard “AutoRABIT Connector” entry. Do not use “AutoRABIT Connector (Dev).”</em></p></figcaption></figure>

#### 7. Edit Policies

On the AutoRABIT Connector page, open the Policies tab and click “Edit.”

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FWi6oIzVH4Pu1XTIpJJOl%2Fimage.png?alt=media&amp;token=0fb61fb9-9129-41e7-972c-6889dfa964e1" alt=""><figcaption><p align="center"><em>Figure 22. Edit action on the AutoRABIT Connector Policies page.</em></p></figcaption></figure>

#### 8. Expand OAuth Policies and enable guest-user credential flow

Expand “OAuth Policies,” enable “Enable Code and Credentials Flow for Guest Users,” and then save the changes.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fko1ZSal3IfYigt87BZET%2Fimage.png?alt=media&amp;token=9a2b099d-e71f-43b3-8fe2-e66a98012015" alt=""><figcaption><p><em>Figure 23. OAuth Policies section before enabling the option.</em></p></figcaption></figure>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F916IpJ1NOuQHwzQcTjfP%2Fimage.png?alt=media&amp;token=5da3587f-2c23-445c-a457-5c17db98e07a" alt=""><figcaption><p><em>Figure 24. “Enable Code and Credentials Flow for Guest Users” enabled.</em></p></figcaption></figure>

## 6. Open the AutoRABIT Connector and Authorize the Inbound Connection

#### 1. Launch AutoRABIT Connector

Open the Salesforce App Launcher, search for “AutoRABIT Connector,” and launch the app.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FARefXOeGN0fcttvrzTck%2Fimage.png?alt=media&amp;token=944a54cb-4b35-45b6-bd3f-eab4f5de6db5" alt=""><figcaption><p>Figure 25. AutoRABIT Connector in the Salesforce App Launcher.</p></figcaption></figure>

#### 2. Open Configuration

From the AutoRABIT Connector home page, click the “Configuration” card.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FlnDyKfbX6pnSHyHjTZLd%2Fimage.png?alt=media&amp;token=f3404426-25a0-494c-a655-7315f3245f2e" alt=""><figcaption><p>Figure 26. Configuration card in AutoRABIT Connector.</p></figcaption></figure>

#### 3. Authorize the inbound connection

The System Connections page contains two authorization areas. Start with Inbound Connection and click “Authorize.” The Salesforce user that completes this authorization becomes the AutoRABIT integration user for the connection.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FjANyrVYtkOOHoWKjBGMx%2Fimage.png?alt=media&amp;token=98e3db65-859c-4880-929b-071abe453403" alt=""><figcaption><p>Figure 27. Inbound Connection authorization in AutoRABIT Connector.</p></figcaption></figure>

{% hint style="danger" %}
**INTEGRATION USER REQUIREMENT** If the currently signed-in Salesforce user is not the intended integration user, use the “Not you?” option on the Salesforce authorization screen and sign in as the correct user. The user completing this authorization must have the “AutoRABIT Setup User” permission set.
{% endhint %}

{% hint style="warning" %}
**NON-ADMINISTRATOR PROFILE REQUIREMENT** If the Salesforce user connecting the org to the AutoRABIT product is not a System Administrator, their profile must also include the following permissions: API Enabled, Modify Metadata Through Metadata API Functions, and Customize Application.
{% endhint %}

#### 4. Allow access

Review the Salesforce authorization request for AutoRABIT Connector and click “Allow” when the displayed user is the intended integration user.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FqJIaieA5ZVKZv2iX7FwR%2Fimage.png?alt=media&amp;token=fc69139b-21b5-4f17-a2d0-48a3b1dadf31" alt=""><figcaption><p><em>Figure 28. Salesforce “Allow Access?” authorization screen.</em></p></figcaption></figure>

## 7. Configure and Authorize the Outbound Connection

After inbound authorization succeeds, complete the Outbound Connection. The connector requires three values from ARM: Subdomain, Client ID, and Client Secret.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FsR29UVZ2u5VuM4neCYxJ%2Fimage.png?alt=media&amp;token=ce1453fd-a1ab-4875-bd2d-dd0887fd09c7" alt=""><figcaption><p align="center"><em>Figure 29. Outbound Connection fields in AutoRABIT Connector.</em></p></figcaption></figure>

#### 1. Sign in to the AutoRABIT product

Open ARM and sign in.

{% hint style="warning" %}
**CREDENTIAL HANDLING** Client Secret values are sensitive. Copy them only into the intended connector field and avoid placing them in tickets, chat messages, or documentation.
{% endhint %}

### 7.1 ARM – Register a Salesforce Org

**1. Open Salesforce Org settings**

In ARM, go to Settings → Salesforce Org. This page lists the Salesforce orgs already registered to this product. To register a new one, click “Register Salesforce org” in the top right.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FzGnUWiL79KAEEXCotSym%2Fimage.png?alt=media&amp;token=b7075ac0-a802-484b-ab72-4b432832ee43" alt=""><figcaption><p><em>Figure 30. ARM Settings → Salesforce Org, with “Register Salesforce org” in the top right.</em></p></figcaption></figure>

**1. Choose the registration method**

In the “Register Salesforce Org” panel, keep “AutoRABIT Connector” selected under Registration method. Click the “Select Salesforce Org” dropdown to see Salesforce orgs already authorized through the AutoRABIT Connector.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FeWrFMAEqx8t0ryQg8GqK%2Fimage.png?alt=media&amp;token=33edbea0-edc3-47b6-b0d3-aade1f9374d9" alt=""><figcaption><p>Figure 31. Register Salesforce Org panel, AutoRABIT Connector method selected.</p></figcaption></figure>

**3. Select an already-authorized org, if available**

If the org you want to add already appears in the list, select it and skip to step 7.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FGDSHuLmquSogSfXtwP8S%2Fimage.png?alt=media&amp;token=cc590c94-9d46-415a-8880-ca0071969865" alt=""><figcaption><p>Figure 32. Select Salesforce Org dropdown showing orgs already authorized with the AutoRABIT Connector.</p></figcaption></figure>

#### 4. If the org isn’t listed, get the connector values from ARM

If you don’t see the org you need in the dropdown, expand “Authorize Org with AutoRABIT Connector” in ARM. This reveals the Subdomain, Client ID, and Client Secret for the org you want to connect.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FtMJw9cmfcbJFpQ0P5n1K%2Fimage.png?alt=media&amp;token=ad554171-c194-4420-acba-d0377777d452" alt=""><figcaption><p><em>Figure 33. Authorize Org with AutoRABIT Connector, expanded to show the Subdomain, Client ID, and Client Secret to copy into Salesforce.</em></p></figcaption></figure>

**5. Enter those values in Salesforce and authorize**

Switch to the Salesforce tab with AutoRABIT Connector open (Configuration → System Connections → Outbound Connection, shown earlier in Section 7). Paste the Subdomain, Client ID, and Client Secret from ARM into the matching fields, then click “Authorize.” Confirm the Outbound Connection changes from “Not Authorized” to an authorized state before continuing.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FYTkCREGQgFbEg5mPhyc9%2Fimage.png?alt=media&amp;token=ed9c64ea-a8c1-459a-b9cf-47cd5b773d67" alt=""><figcaption><p><em>Figure 34. Outbound Connection fields in Salesforce populated with the values copied from ARM, ready to authorize.</em></p></figcaption></figure>

**6. Return to ARM and select the newly authorized org**

Back in ARM, reopen the “Select Salesforce Org” dropdown from step 3. The org you just authorized should now appear in the list — select it.

**7. Add the org**

Once the org is selected, click “Add Org” in ARM to complete the registration.

{% hint style="info" %}
**ABOUT THIS SECTION** ARM's registration panel doesn't show a separate first-time “welcome” screen the way some other AutoRABIT products do — the same panel is used whether this is the first org or an additional one. If ARM does expose a distinct first-time flow, let me know and I'll split this into first-time / adding-another-org subsections to match the source procedure's pattern exactly.
{% endhint %}

## 8. Enable Products and Assign Permissions

#### 1. Open Products

After system connection registration is complete, close Configuration and open the “Products” card in AutoRABIT Connector.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FtjXaAYy09hsnSyvYrJgG%2Fimage.png?alt=media&amp;token=f4b99c59-7796-4aa1-898e-ec1b6fdd912c" alt=""><figcaption><p>Figure 35. Products card in AutoRABIT Connector.</p></figcaption></figure>

2. Review product availability and toggles

For products with valid licenses, the connector displays an enable/disable toggle. Enabled products can see the registered Salesforce org in the related AutoRABIT application. If the toggle is off, that product cannot use the org in its configuration.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FYe9SxvacPvJWjTQ9JK4P%2Fimage.png?alt=media&amp;token=24df02a4-730c-4c0e-ae8c-d45329a1b3de" alt=""><figcaption><p>Figure 36. Example of a licensed product enabled with its toggle (a different AutoRABIT product is shown here as the illustrative example from the source procedure; ARM's own toggle appears the same way when licensed).</p></figcaption></figure>

{% hint style="info" %}
**DEFAULT BEHAVIOR** After the org is registered, available licensed products are enabled by default in the flow shown. Turn off a product only when the org should not be exposed to that application.
{% endhint %}

#### 3. Recognize products without a license

If there is no valid license for a product, the product page displays that no valid licenses are available instead of an active enablement toggle.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FqMObuCdI7cdjLwrD8LPu%2Fimage.png?alt=media&amp;token=a246dfc2-b724-4c71-b2f2-17792f2f8ac5" alt=""><figcaption><p>Figure 37. Example of a product with no valid licenses available (shown for a different product in the source procedure; this guide assumes ARM itself is licensed).</p></figcaption></figure>

#### 4. Open Licensing & Permissions

Return to the AutoRABIT Connector home page and click “Licensing & Permissions.”

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FzoIdbzqoQU6NpPalIrRK%2Fimage.png?alt=media&amp;token=110329c6-bac9-44fe-bdb6-354fbaf86421" alt=""><figcaption><p>Figure 38. Licensing &#x26; Permissions card.</p></figcaption></figure>

#### 5. Assign the required permission sets

Review the listed AutoRABIT permission sets and assign the AutoRABIT ARM permission set to the authorized/integration user. The detailed steps for configuring this permission set are in section 8.1 below.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FeQwo5BA5pWBGU4gO6JoP%2Fimage.png?alt=media&amp;token=b04c629c-4ddb-4ae9-a682-a918e5a712f9" alt=""><figcaption><p>Figure 39. AutoRABIT permission sets available from Licensing &#x26; Permissions.</p></figcaption></figure>

8.1 AutoRABIT ARM Permission Set This section walks through configuring the AutoRABIT ARM permission set in Salesforce. Follow each step in order to grant the AutoRABIT ARM integration user the access it needs.

1. Open Licensing & Permissions In Salesforce, open the AutoRABIT Connector app and click Licensing & Permissions.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FzIKubekQx24wyUyxh7tT%2Fimage.png?alt=media&amp;token=2d003a4e-4016-47c4-b8df-ec3f599183ed" alt=""><figcaption><p>Figure 40. AutoRABIT Connector home page, with Licensing &#x26; Permissions highlighted.</p></figcaption></figure>

**2. Open Permission Sets**

Click Permission Sets.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FG0x5ZyaeasKXoy4WoB8u%2Fimage.png?alt=media&amp;token=d99ce70f-eec3-43fb-95be-66f5ae5e50cd" alt=""><figcaption><p>Figure 41. Permission Sets option under Licensing &#x26; Permissions.</p></figcaption></figure>

**3. Select the AutoRABIT ARM Permission Set**

Click AutoRABIT ARM to open the permission set.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FyIWFChf8eoQp7plcKtm3%2Fimage.png?alt=media&amp;token=96c9fb28-5b58-4d7d-87e2-20ac7c227033" alt=""><figcaption><p>Figure 42. AutoRABIT ARM permission set in the Permission Sets list.</p></figcaption></figure>

**4. Open System Permissions**

Click System Permissions. This section controls permissions to perform actions that apply across apps, such as “Modify All Data.”

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FQDuaLEj2ichhe3udcFgd%2Fimage.png?alt=media&amp;token=b6680501-8ff7-4881-abba-7433c59512f1" alt=""><figcaption><p>Figure 43. System Permissions option on the AutoRABIT ARM permission set.</p></figcaption></figure>

**5. Enable editing**

Click Edit to make the permission list editable.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F4nUkC0TRp3SsoQ5AWwHE%2Fimage.png?alt=media&amp;token=84f4a918-446c-4f42-9463-9cec15644651" alt=""><figcaption><p>Figure 44. Edit action on the AutoRABIT ARM System Permissions page.</p></figcaption></figure>

**6. Enable View All Data**

Search for View All Data and select its checkbox if it is not already selected.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FMapxlFYyCrHd9qbbgdyb%2Fimage.png?alt=media&amp;token=d3663091-10c4-4a98-bbe0-42540ccf12d0" alt=""><figcaption><p align="center"><em>Figure 45. Searching for and enabling View All Data.</em></p></figcaption></figure>

&#x37;**. Enable Modify All Data**

Search for Modify All Data and select its checkbox if it is not already selected.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FH4JfOCRx5ie69GqtMyLK%2Fimage.png?alt=media&amp;token=93b4c355-ddd4-4563-b5a3-1586180c2d4f" alt=""><figcaption><p align="center"><em>Figure 46. Searching for and enabling Modify All Data.</em></p></figcaption></figure>

**8. Enable Customize Application**

Search for Customize Application and select its checkbox if it is not already selected.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FSadqteBlUzB6iYJ4QPIy%2Fimage.png?alt=media&amp;token=4bf50e9a-8189-4c69-b172-08340237bf2f" alt=""><figcaption><p align="center"><em>Figure 47. Searching for and enabling Customize Application.</em></p></figcaption></figure>

**9. Enable Manage Users**

Search for Manage Users and select its checkbox if it is not already selected, using the same System Permissions search-and-enable pattern shown in the previous step.

**10. Save the permission set**

After selecting all the required checkboxes, click Save at the top of the page.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FEzxvkiTVSLuvPkkT7Co9%2Fimage.png?alt=media&amp;token=bcc52fd9-d601-4ad5-b152-acb74f19a2b6" alt=""><figcaption><p>Figure 48. Save action on the System Permissions page.</p></figcaption></figure>

**11. Confirm the save**

In the Save Changes confirmation dialog box, click Save again to apply the changes.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FfMHiC5J3FUSsFk9mtPgd%2Fimage.png?alt=media&amp;token=491c9b30-47b3-4ff3-8f57-a162b33fad6f" alt=""><figcaption><p><em>Figure 49. Save Changes confirmation dialog listing the permission dependencies.</em></p></figcaption></figure>

{% hint style="info" %}
**ALTERNATIVE: OBJECT-BY-OBJECT PERMISSIONS** If you do not want to grant all View All Data and Modify All Data permissions at once, you can go back to step 4 and, instead of System Permissions, open Object Settings. From there, grant the required permissions object by object, based on your specific needs.
{% endhint %}

## 9. Complete Salesforce Org Registration in ARM

#### 1. Refresh the product-side org list

After the Salesforce-side registration and permissions are complete, return to the ARM “Register Salesforce Org” panel and click the refresh icon next to the “Select Salesforce Org” dropdown.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F7kXligeILT1XqcIxia46%2Fimage.png?alt=media&amp;token=8f1a5e3e-0c57-40f7-812a-8ffce171141b" alt=""><figcaption><p>Figure 50. Refresh control next to the Select Salesforce Org dropdown in ARM.</p></figcaption></figure>

#### 2. Select the newly authorized Salesforce org

The newly authorized Salesforce org should now appear in the dropdown. Choose it to create the product configuration.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FGDSHuLmquSogSfXtwP8S%2Fimage.png?alt=media&amp;token=cc590c94-9d46-415a-8880-ca0071969865" alt=""><figcaption><p>Figure 51. Select Salesforce Org dropdown in ARM, now showing the newly authorized org.</p></figcaption></figure>

#### 3. Add the org

With the correct org selected, click “Add Org.”

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fd3pAm6H2wECE0mpmANBj%2Fimage.png?alt=media&amp;token=e24e10e3-7ff5-492c-b5ed-d1f1375d928b" alt=""><figcaption><p align="center"><em>Figure 52. “Add Org” action in the ARM Register Salesforce Org panel.</em></p></figcaption></figure>

{% hint style="info" %}
**CROSS-PRODUCT BEHAVIOR** Once the Salesforce org has been configured for one AutoRABIT product, any other AutoRABIT application that has a valid license and is enabled for the org should display that org without repeating the connector configuration steps.
{% endhint %}

## 10. Completion Checklist

Before handing the configuration over for use, verify each item below.

☐ AutoRABIT package installation completed successfully in the intended Salesforce org.

☐ Required OAuth settings are enabled in Salesforce Setup.

☐ “Lock sessions to the IP address from which they originated” is disabled in Session Settings.

☐ AutoRABIT Connector OAuth Policy is saved with Code and Credentials Flow for Guest Users enabled.

☐ The standard “AutoRABIT Connector” ECA is selected; “AutoRABIT Connector (Dev)” is not used for normal configuration.

☐ Inbound Connection is authorized with the intended integration user.

☐ The integration user has the AutoRABIT Setup User permission set.

☐ Outbound Connection contains the correct Subdomain, Client ID, and Client Secret and shows as authorized.

☐ ARM is enabled in the Products area.

☐ The AutoRABIT ARM permission set is configured and assigned to the authorized user.

☐ The Salesforce org appears in ARM after Refresh.

☐ The org was successfully added to the ARM product configuration.

{% hint style="warning" %}
**IF SOMETHING DOES NOT APPEAR** Recheck the package installation status, OAuth settings, connector authorization state, product license availability, the product enablement toggle, and the permission sets assigned to the integration user. The product-side org list may also need to be refreshed after Salesforce-side changes.
{% endhint %}


---

# 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://knowledgebase.autorabit.com/product-guides/arm-1/getting-started/signing-up-with-arm/autorabit-arm-app-installation-and-configuration-guide.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.
