to navigate to open Esc to close Search by Algolia

Collaborative editing

FileRun can open office documents in an editor that runs in the browser, so several people can work on the same file at once. The document stays in FileRun; the editor only borrows it while it is open.

Five editors can do this, and they fall into two groups.

Editors you install yourself

These are separate servers that you run on your own infrastructure. FileRun talks to them over the network, using the WOPI protocol, and the documents never leave your systems.

Editors that are online services

These need nothing installed, but the provider's servers fetch the document from your FileRun installation, so it has to be reachable from the Internet.

Where they are configured

All of them are configured in the control panel, under FilesPlugins. Select the plugin and click Edit.

To make one of them the editor that opens when a user double-clicks an office document, set it as the default under FilesPluginsDefaults. Otherwise it is offered in the Open with.. menu.

Other ways of previewing and editing documents, including the ones that do not edit together, are listed on File preview options.

What the self-hosted editors have in common

Collabora Online, ONLYOFFICE Docs and LibreOffice Online share the same two settings.

Document editing service URL

The address of the editor server, for example http://localhost:9980.

The protocol has to match. If FileRun is served over https://, the editor URL must be https:// as well; if FileRun runs on plain http://, so must the editor. FileRun refuses a URL whose protocol differs from its own, because editing would not work.

When you save a new URL, FileRun contacts the editor and reads its WOPI discovery document. It confirms this with Document editing service successfully validated!. If it cannot reach the editor, or the answer is not a WOPI service, the settings are refused and nothing is saved — so a saved setting is one that was proven to work.

Verify SSL certificate

Leave this on. You can turn it off when the editor server is inside your own network and uses a certificate that your FileRun server does not trust.

The browser reaches the editor too

The editor is loaded by the person's browser, not only by the FileRun server. The address you configure has to be reachable from both. An address such as http://localhost:9980 works only when FileRun and the editor run on the same machine as the browser, which is normally true just while testing.

For everyday use, publish the editor under a hostname your users can reach, with a certificate that matches, and use that hostname in the setting.