Install one package, and documents open in a real engine.

Our connector for SuiteCRM is an ordinary Module Loader package. It adds an Open in SumOffice field to the document record and a complete WOPI host behind it — and the rights come from the document's own ACL, not from a second set of permissions you have to maintain. Measured on SuiteCRM 8.9.1.

What was measured

The round	A macro workbook and a document with five pictures: opened from SuiteCRM, edited, saved back. VBA byte for byte, pictures byte for byte, the edit in place.
The refusals	We also checked what happens when things are wrong, because that is where connectors usually leak: a request with no signature or a forged one — 500; someone else's revision or a corrupted token — 401; rubbish in the path — 404.
Rights	Read and write follow the document's ACL in SuiteCRM. No parallel permission model.
What this does not say	The fixture workbook these rounds used asks Microsoft Excel to repair it on its own, before any round — so no silent-Excel claim here. See Nextcloud and Seafile.

Setting it up

# the editors, behind your TLS address
git clone https://github.com/SumOfficeApp/sumoffice-docker && cd sumoffice-docker/nextcloud
cp env.example .env    # PUBLIC_URL=https://office.example.com
docker compose up -d

# the package: sumoffice-docker, branch integrations, folder integrations/suitecrm
# SuiteCRM → Admin → Module Loader → upload and install

Evaluation is free with no time limit; production is the per-application license. The other systems we measured →

Then

Check my Excel file — in seconds, without running anything.
Tell us your SuiteCRM version — 8.9 is measured.