Installing REDA Connect

REDA Connect installs like any Salesforce managed package: open the install link, sign in to the org you want to install into, and confirm. The installation itself takes a few minutes; afterwards nothing is switched on yet — users get access through permission sets, and messaging starts working only after the setup steps in the Setup roadmap. This article covers the install, what lands in your org, how to verify the installed version, and the one manual step upgrades need.

Step 1 — Get your install link, then open it

REDA does not publish install links publicly. Package versions change with every release, and the right link depends on the edition and version you are licensed for — so the link comes to you directly.

1. Request the install link for REDA Connect from your REDA account executive, or email support@reda.one. If you have already been onboarded, the link may also be in your onboarding materials. Tell them which org you are installing into (sandbox or production) and they will give you the correct link for your edition and the current release.
2. Open that link in your browser.
3. Sign in with the username of an administrator of the target org (double-check the org — the install goes wherever you sign in).

Expected result: the package installation page opens, showing the package name REDA Connect and the version being installed.

Step 2 — Choose "Install for Admins Only" and confirm

1. On the install page, select Install for Admins Only. This is the recommended option: it grants nothing to regular users at install time, and you give your team access deliberately afterwards, through the packaged permission sets — see Giving your team access.
2. If Salesforce asks you to approve access to third-party websites, tick the approval box and continue. These are the messaging providers' addresses (api.twilio.com for Twilio and graph.facebook.com for WhatsApp) that the package registers so your org can call them.
3. Click Install and wait. Large packages sometimes finish in the background — if you see "This app is taking a long time to install", you will get an email when it completes.

Expected result: an "Installation Complete!" confirmation on screen (or by email), and REDA Connect appears under Setup → Installed Packages.

Step 3 — Verify the installed version

1. In Salesforce, click the gear icon (top right) and choose Setup.
2. In the Quick Find box, type Installed Packages and click Installed Packages under Apps → Packaging.
3. Find the row named REDA Connect and check its Version Number.

Expected result: REDA Connect is listed with version 1.93 or later. This documentation set is verified against 1.93 — if your version is older, upgrade before following these articles.

Installed Packages showing REDA Connect with its version number

What gets installed

The following components are installed together inside your Salesforce org. Messaging also requires configuration of the external Meta or Twilio service used by your channel:

Upgrading from an earlier version

Upgrades install over the existing package with the same link and keep all your data and configuration. Two things to check after upgrading to 1.93 or later:

1. Swap the "(Deprecated)" quick actions. Version 1.93 replaced five quick actions with modernised versions that keep the familiar names; the old ones remain but are now labelled "(Deprecated)". Salesforce does not change your existing page layouts on upgrade, so layouts you have customised may still carry the old buttons. On each layout, remove the deprecated action and add its replacement:

   Where (Object Manager → object → Page Layouts)	Remove	Add instead
   Connect Template	Test Connect Template (Deprecated)	Test Template
   Connect Template	Activate Template (Deprecated)	Activate Template
   Connect Template	Deactivate Template (Deprecated)	Deactivate Template
   Connect Account	Update WhatsApp Auth Token (Deprecated)	Update WhatsApp Auth Token
   Connect Account	Update SMS API Tokens (Deprecated)	Update SMS API Tokens

   The replacements run the same logic and show the same messages — only the buttons need swapping.

2. Note the two Connect Feed tabs. 1.93 introduced a rebuilt Connect Feed. The tab named Connect Feed is the current one; the old tab is now labelled Connect Feed (Deprecated) and is reachable only from the App Launcher, kept so old bookmarks still work. Point your team at the current tab, and when placing the feed on pages in Lightning App Builder, always pick the component without "(Deprecated)" in its name — see Adding the feed to a record page.

The old and new actions sitting next to each other in Object Manager → Connect Template → Buttons, Links, and Actions. The pattern is easy to read once you see it: the current action is a Lightning Web Component with a Connect_ prefix on its API name, the retired one is a Lightning Component without it. The shipped description says why both still exist — “a packaged quick action cannot be deleted” — so the retired ones stay in this list forever and it is your page layouts that need changing, not the object.

FAQ

Where to go next

• Giving your team access — assign the permission sets so people can actually see the app.
• Setup roadmap — install to first message — the full ordered checklist that starts where this article ends.
• Creating the public Site for incoming messages — the first hands-on setup step after installing.