Documents from Confluence and your intranet wiki ask about your work instructions instead of clicking through spaces.

Confluence in the cloud connects in one click via your Atlassian account and is included in the set-up, subject to admin consent in your account – details are on the Confluence page. A SharePoint wiki comes across through the Microsoft 365 connection, also in one click and included in the set-up. A self-hosted intranet wiki, including Confluence on your own server, is subject to a feasibility check: the content sits in a database, not in folders, so the route is an agreed, scheduled export of the chosen areas including attachments, sent encrypted and over outbound connections only to your instance. The page tree comes along so that each page’s origin is recorded, and a person confirms the suggested document type. We check before we start whether and how such a wiki can be connected – whether an interface exists, is enabled and reachable, and whether the account used is allowed to export spaces, depending on version, licence and hosting model. Until then you can upload exports by hand, as files or whole folders.

Once set up, synchronisation runs automatically: new and changed documents from Wiki and intranet are added without anyone having to upload anything.

Set-upConfluence in the cloud and a SharePoint wiki: one click, included in the set-up, subject to admin consent in your account. For a self-hosted wiki, we estimate the work involved once it is clear which areas should come across and which export route is available, and discuss it with you before anything is set up – ideally together with your wiki administrator. That set-up is charged on a time-and-materials basis, agreed in advance.

This connection is set up for you rather than switched on in one click. Every source has its own logins, permissions and folder structure – so before we start, we check with you whether and how it can be connected at your company. Set-up and maintenance are charged on a time-and-materials basis, agreed in advance; the amount depends on the source.

You can also upload files, whole folders, emails, photos and voice notes at any time. In the demo you see the answers using sample documents from your industry; you check them against your own documents in the first weeks after go-live.

Before we start, we look at which pages are out of date: many wikis keep older versions alongside the current ones, and the 2019 instruction often looks just as valid as today’s. You decide which version applies – outdated content can be left out or flagged; nothing in the wiki itself is touched. We also check how dynamically assembled content – embedded lists, status overviews, diagrams from add-ons, links into other tools – comes across; depending on the add-on, it may arrive as just an image or a blank space. Whether page comments, older versions and unpublished drafts are included depends on the route; since the real decision is sometimes buried in the comments, we agree this with you beforehand.