Template Porter for Confluence documentation
Documentation for Template Porter for Confluence. It describes the application as it exists today.
Requirements
- Confluence Cloud.
- Space administrator permission to write templates in a space; Confluence administrator permission for global templates.
- To import into another site, the app must be installed on both sites.
How a run works
- Choose global templates or a space and select the templates.
- Export them to a JSON file, or choose target spaces to copy to, or upload a file to import.
- Review the preview: create, skip, rename or overwrite for each template, and pick the clash policy.
- Confirm. The target is read again just before writing.
- Download the CSV report.
Limits you should know
- Up to 200 templates and 5 MB per file in one run.
- Blueprint templates are not supported.
- Mentions, page links and attachments inside a template are flagged but not rewritten; check them in the target.
Permissions and temporary data
- The six Forge scopes are read:template:confluence, read:content-details:confluence, write:template:confluence, read:space:confluence, storage:app and report:personal-data.
- Each pending plan record has a 24-hour Forge KVS TTL. The application refuses access when the plan reaches 24 hours, even if Forge's physical TTL cleanup is still finishing.
- A weekly Forge task reports account IDs found inside temporary ri:user mentions to Atlassian's Personal Data Reporting API, using the earliest retrieval time held for each account.
- If Atlassian marks an account closed or updated, the whole pending plan that contains it is deleted rather than rewriting part of the template body.