The simplest way to install Relm Pro for Excel is from Microsoft AppSource. AppSource handles updates automatically, works across Excel for Windows, Mac, and the web, and respects your organization's IT policy.
Before you start
- A Microsoft account for the Excel where you'll install the add-in.
- A Relm Pro account at relm.ai — you'll sign in with this from the add-in's taskpane after install.
- Excel 2019 or later on Windows or Mac, or current Excel for the web. Older versions don't run modern Office Add-ins.
Install
- Open Excel.
- Go to Insert → Get Add-ins (Windows) or Insert → Add-ins (Mac/Web).
- Search for Relm Pro.
- Click Add.
The add-in installs into your Excel and shows up as a Relm Pro ribbon tab.
First open
- Click the Relm Pro tab on the ribbon.
- Click Open Taskpane.
- The Relm Pro taskpane appears on the right side of Excel.
- The taskpane shows a Sign in prompt.
- Click Sign in — Excel opens a browser window for the device-link sign-in flow.
Org-wide deployment
If your IT or M365 admin manages add-ins centrally, they can deploy Relm Pro to your team via the Microsoft 365 admin center → Integrated apps. Once deployed, every user in the assigned group sees Relm Pro automatically.
This is the recommended path for teams of more than ~5 people. Talk to your account contact for the IT-deployment package.
Updating
Updates ship via AppSource. Most ride out without explicit user action — the next time you open Excel, you have the latest version. If you ever need to force a refresh, see Update / reload the add-in.
When AppSource isn't an option
If your organization restricts AppSource access (locked-down IT environments), you can sideload the add-in via a manifest file. See Sideload manifest.
Common issues
- "Add-in won't load." Excel sometimes caches an older bundle. Close and re-open Excel; if still failing, see Excel troubleshooting.
- "This add-in is not approved for your tenant." Ask your M365 admin to whitelist it via Integrated Apps.
- Mac-specific. On Mac, Excel sometimes fails to load taskpane web content if a system trust setting is missing — see Trust the localhost cert (Mac dev) for the symptoms (mostly only relevant for our internal dev builds, but worth a check).