Documentation
Word Exporter for ConfluenceBrowse
Documentation
Word Exporter for ConfluencePricing & Permissions
Pricing
Word Exporter for Confluence is free. There is no trial period, no license key and no paid tier. It is coming soon to the Atlassian Marketplace.
Permissions
Who Can Export
Any Confluence user with at least view permission on a page can open Word Exporter and export that page. No additional app-level permissions are required for basic export access.
Who Can Configure Templates
Only Confluence site admins can access Confluence Settings → Word Exporter to create, edit, archive, or delete templates.
Space admins and regular users cannot manage templates.
Scheduled Exports
Any user can create a schedule for content they can view, delivering to a page they can edit. Every run uses the schedule owner's access: pages the owner can't view are left out. Site admins can see, pause and delete every schedule.
API Tokens
Only site admins can create API tokens. A token acts as the admin who created it: an export started with it includes only pages that admin can view, and can only be attached to pages they can edit.
App Scopes
Word Exporter for Confluence requests the following Confluence API scopes during installation:
| Scope | Purpose |
|---|---|
| Read pages and spaces | Fetch page content for export |
| Read attachments | Include images and files in exports |
| Read content hierarchy | Build the hierarchical page tree |
| Search Confluence | Power the page search feature |
| App storage | Store templates, schedules, API tokens and background exports |
| Write attachments | Attach scheduled and API exports to the archive page you choose |
| Write comments | Post the @mention comment that emails people about scheduled and API exports |
| Read user details | Show who owns a schedule or token, and fill in {lastEditedBy} in background exports |
| Read content details | Required by Confluence, with Write attachments, to upload a file to a page |
Scheduled exports and API exports run while their owner isn't signed in. To check what the owner may see, the app reads pages as that user (Atlassian calls this offline user impersonation) and never uses its own, wider access to decide what's exported.
No content is stored outside Atlassian infrastructure, and no data is sent out of Atlassian. The app runs entirely on Atlassian Forge.
Stuck on something this page does not cover? Ask the developers.