Requirements¶
Lime CRM¶
- Lime CRM 3.80.0 or newer.
- The Lime CRM backend must be reachable over HTTPS from the users' devices. Office add-ins do not load over plain HTTP.
- A JWT signing key must be set in the application configuration before users can sign in. See Configuration.
Hosting¶
Lime Cloud only.
This follows directly from the version requirement: the add-in needs Lime CRM 3.80.0 or newer, and the latest on-premise release line is 3.47.x. On-premise installations therefore cannot run the add-in today.
On-premise Redis setting
The Redis configuration described under Configuration exists for on-premise deployments, but it does not make the add-in usable on-premise while the version requirement is unmet. On Lime Cloud, Redis is provided by the platform and needs no configuration.
Lime CRM web client¶
The add-in's save form is the Lime CRM web client, so the limetypes it saves to must already have a working card view there — typically History, Document, and whichever limetype receives the email (Deal, Ticket, Company, Person, or others). If these limetypes already work in the web client, no extra setup is needed for the add-in.
Users don't need to switch to the web client for their day-to-day work — the desktop client remains fully usable for everything else. The one limitation: the desktop client does not render rich text formatting or inline images, so a record saved by the add-in shows raw markup there instead of a formatted email. View it in the web client to see it as intended.
Outlook¶
| Client | Supported |
|---|---|
| New Outlook for Windows | Yes |
| New Outlook for Mac | Yes |
| Outlook on the web | Yes |
| Outlook for iOS / Android | Yes — without attachments, and not in shared mailboxes |
| Classic Outlook for Windows | No |
| Classic Outlook for Mac | No |
The add-in requires Outlook Mailbox API 1.3 or newer, which all supported clients provide.
Browser¶
Saving opens Lime CRM in a separate window. Users must allow pop-ups for their Outlook domain (outlook.office.com, or outlook.office365.com). If pop-ups are blocked, clicking Save in CRM appears to do nothing — this is the single most common support call. See FAQ & Troubleshooting.
Live Docs and Selective File Storage¶
If the customer uses Live Docs, do this first
When Live Docs is enabled, every file is pushed to SharePoint by default — including every email attachment and every .eml file the add-in generates. Saving an email becomes painfully slow, and users will complain.
Configure Selective File Storage so that Office documents go to Live Docs and everything else goes to the database or S3.
Microsoft 365 tenant¶
- Users need a mailbox in Microsoft 365 (Exchange Online).
- IT must be able to deploy an Office add-in to users — through the Microsoft 365 admin center, or by allowing users to install one themselves. See Deploying to Outlook.
- If the tenant uses Microsoft Entra Conditional Access, note the mobile limitation.
What the setup person needs¶
Before starting the Configuration checklist:
- Access to Lime Admin for the solution.
- Ability to change the application configuration (to add the signing key).
- Knowledge of whether the customer uses Live Docs.
- A contact in customer IT who can deploy the manifest.