What the Confluence integration does
Bring everything over in an afternoon: clients, sites, contacts, configurations, passwords and documents.
Setting it up
Confluence spaces come into the knowledge base. Go to Admin › Import & export › Switch to DokLocker › From Confluence.
- Confluence Cloud (an address ending in atlassian.net): make an API token at id.atlassian.com › Security › API tokens, and enter it with the email address of that account.
- Confluence Data Center or Server: make a personal access token under your profile › Personal access tokens, and leave the email empty.
DokLocker reads every space the account can see and shows how many pages and images each one has. Tick the spaces to bring in. If a space is only about one client, pick that client next to it (a space named like a client is picked for you); the rest apply to every client.
| In Confluence | In DokLocker |
|---|---|
| Space | A knowledge base folder |
| Page tree | Pages under pages, in the same order |
| Info, tip, note and warning panels | Info, tip, warning and danger boxes |
| Expand | A collapsible section |
| Table of contents macro | [TOC] |
| Code blocks | Code blocks, with the language kept |
| Task lists, tables, links, headings | The same |
| Links to other pages | Links to the imported pages |
| Images attached to a page | Images on the page (page files) |
| Children, page tree and search macros | Left out; the DokLocker page tree does this |
Pages already in that folder with the same title are left alone, so you can run it again to pick up new pages. The token is kept encrypted only until the import finishes, then deleted with the rest of the read.
Included in every plan
Every integration is included at no extra cost, on the hosted service and self-hosted. Connect it under Admin › Integrations, click Test, and the first sync starts straight away.