Atlassian trouble? Talk to us.
Confluence gets more expensive, moves to the cloud and decides where your data lives. doc.handel takes over your content without loss and keeps it in Switzerland.
What doc.handel does differently
Not another notes tool, but a wiki with Confluence’s feature set — and three things Confluence cannot do.
Import from the space export
Pages, page tree, attachments, labels and internal links come along, every old Confluence address redirects. Versions, comments and permissions follow; the trial-run report tells you beforehand what is missing.
Data sovereignty
Separate data per customer, no shared tables, identity from auth.handel. Operated in Europe; operation in Switzerland on request.
Four languages, one page
A page has up to four language versions. When the lead language changes, doc.handel marks the translations as outdated.
Permissions that hold
One visibility rule for navigation, search, macros and API. What someone may not see never shows up in any hit count.
DMS integration in progress
Goal: attachments in the xecm.handel DMS, pages as PDF/A records, DMS documents as cards in the wiki, without a copy. Today: PDF export per page and subtree.
The macros you know
Table of contents, child pages, include, page properties, task report, draw.io — and a visible placeholder for anything unknown.
Integrations
doc.handel is part of the handel family: documents and identity come from the same services as sales, hr and finance.
Enterprise Content Management
Every attachment is a node in the DMS. Retention, disposal and WORM belong there, not in the wiki.
Sign in with Microsoft, Google, Apple or a HIT account
Users and groups come from auth.handel. No second user directory, no second set of permissions.