Richdocuments integrates Collabora Online with ownCloud Server, enabling real-time collaborative editing of documents, spreadsheets and presentations directly within the ownCloud web interface. The app uses the WOPI (Web Application Open Platform Interface) protocol to bridge ownCloud's file storage with the Collabora Online document editing server.
This app is part of the ownCloud Server ecosystem, providing online document editing capabilities through the Collabora Online integration. It is available on the ownCloud Marketplace.
Branch master targets ownCloud Server 11 (PHP 8.3); branch 4.2 targets ownCloud Server 10.11 and
later (PHP 7.4). See appinfo/info.xml for the authoritative version constraints.
The ownCloud Server is available on Docker Hub.
Follow the steps below to install and configure Collabora Online integration.
Install from the ownCloud Marketplace, or manually from the root of your ownCloud Server installation:
git clone https://github.com/owncloud/richdocuments.git apps/richdocuments
php occ app:enable richdocumentsThe Collabora Online server must be reachable from the ownCloud server, and the ownCloud server must be reachable from the Collabora Online server. It is also possible to use Collabora Online's integration with re-compiled and/or re-branded backends.
Set the WOPI server URL:
occ config:app:set richdocuments wopi_url --value [your-host-public-ip]:8098Alternatively, set the Collabora Online server under
Settings -> Admin -> Additional -> Collabora Online server.
Enable Secure View (requires an ownCloud Enterprise license):
occ config:app:set richdocuments secure_view_option --value true
occ config:app:set richdocuments watermark_text --value "Restricted to {viewer-email}"
occ config:app:set richdocuments secure_view_open_action_default --value trueTo use the app from ownCloud Web you additionally need ownCloud Web itself, either installed as an app or built from source.
Register the connector in the ownCloud Web config.json:
- ownCloud Web installed as an app on the server:
<owncloud-root>/config/config.json - ownCloud Web built from source following these instructions:
<owncloud-web-root>/config/config.json
"external_apps": [
{
"id": "richdocuments",
"path": "http(s)://<owncloud-server-address>/index.php/apps/richdocuments/js/richdocuments.js"
}
]Start a Collabora server for development, with SSL disabled (adjust the image tag to a current Collabora Online release):
docker run -t -d -p 9980:9980 -e "extra_params=--o:ssl.enable=false" \
-e "username=admin" -e "password=admin" \
--name collabora --cap-add MKNOD collabora/code:6.4.8.6The Collabora admin interface is then available at
http://[your-host-public-ip]:9980/loleaflet/dist/admin/admin.html.
Build the ownCloud Web connector (compiles src/ into js/web/richdocuments.js, which is committed):
pnpm install
pnpm buildRun the tests. Note that make test-php-unit resolves PHPUnit inside the surrounding ownCloud Server
tree, so the app has to be checked out as apps/richdocuments:
make test-php-unit
make test-acceptance-webui
make test-php-styleSee AGENTS.md for a fuller description of the layout and the available make targets.
Star this repo and Watch for release notifications!
We welcome contributions! Please read the Contributing Guidelines and our Code of Conduct before getting started.
- Rebase Early, Rebase Often! We use a rebase workflow. Always rebase on the target branch before submitting a PR.
- Dependabot: Automated dependency updates are managed via Dependabot. Review and merge dependency PRs promptly.
- Signed Commits: All commits must be PGP/GPG signed. See GitHub's signing guide.
- DCO Sign-off: Every commit must carry a
Signed-off-byline:git commit -s -S -m "your commit message" - GitHub Actions Policy: Workflows may only use actions that are (a) owned by
owncloud, (b) created by GitHub (actions/*), or (c) verified in the GitHub Marketplace.
Help translate this project on Transifex: https://explore.transifex.com/owncloud-org/owncloud/
Please submit translations via Transifex -- do not open pull requests for translation changes.
Do not open a public GitHub issue for security vulnerabilities.
Report vulnerabilities at https://security.owncloud.com -- see SECURITY.md.
Bug bounty: YesWeHack ownCloud Program
This project is licensed under the AGPL-3.0, as declared in appinfo/info.xml and in the header
of every source file.
Note: this repository does not carry a root
LICENSE/COPYINGfile yet. Adding one is tracked as OSPO follow-up work; it does not change the license that already applies.
The Kiteworks Open Source Program Office, operating under the ownCloud brand, launched on May 5, 2026, to steward the open source ecosystem around ownCloud's products. The OSPO ensures transparent governance, license compliance, community health, and sustainable collaboration between the open source community and Kiteworks, which acquired ownCloud in 2023.
- OSPO Home: https://kiteworks.com/opensource
- GitHub: https://github.com/owncloud
- ownCloud: https://owncloud.com
For questions about the OSPO or licensing, contact ospo@kiteworks.com.
The OSPO is driving a strategic relicensing of ownCloud repositories toward the Apache License 2.0, following the Apache Software Foundation's third-party license policy.
Individual repositories will migrate as their audit is completed. The license declared in each repo reflects its current license status (not the target).
Current license: AGPL-3.0 (Category X per Apache policy -- cannot be included in Apache-2.0 works).
Migration prerequisites for this repository:
- CLA/DCO coverage: All past contributors must have signed agreements permitting relicensing
- Copyleft dependency audit: All AGPL/GPL dependencies must be replaced or isolated
- Third-party heritage review: This app originated as Collabora Productivity work based on code by Frank Karlitschek and Victor Dubiniuk, so its copyright history requires legal analysis
- Complete relicensing: AGPL-3.0 is a strong copyleft license; migration requires full relicensing of all files, not just a header change
- Add a license file: The repository needs a root
LICENSE/COPYINGfile recording its current AGPL-3.0 status before any migration step