Full Space Copy

Hosting and data residency

The app runs entirely on Atlassian Forge and carries the Runs on Atlassian badge. There is no server, no database and no logging service operated by the publisher. Data residency follows your Atlassian site.

Who can start an operation

Only administrators of the source space who are allowed to create spaces can start a copy. Other operations require administering the spaces involved. These permissions are checked by Confluence on every action, on the server side, not only when the screen is displayed. A site administrator can also limit the app to some groups.

Permissions requested

A copy recreates an entire space: pages, blog posts, attachments, settings and access. It therefore needs to read and write most of a space's content. The permissions, grouped by purpose:

• Read and write space content: read:page:confluence, write:page:confluence, delete:page:confluence, read:blogpost:confluence, write:blogpost:confluence, read:folder:confluence, write:folder:confluence, read:whiteboard:confluence, read:database:confluence, read:embed:confluence, write:embed:confluence, read:comment:confluence, write:comment:confluence, read:attachment:confluence, write:attachment:confluence, write:confluence-file, read:label:confluence, write:label:confluence, read:confluence-props, write:confluence-props, read:confluence-content.all, read:confluence-content.summary, write:confluence-content, search:confluence.
• Create the destination space and carry over its settings: read:space:confluence, write:space:confluence, write:confluence-space, read:confluence-space.summary, read:space-details:confluence, read:space.property:confluence, write:space.property:confluence, read:template:confluence, write:template:confluence, read:configuration:confluence, write:configuration:confluence, manage:confluence-configuration.
• Check permissions and carry over access: read:confluence-content.permission, read:space.permission:confluence, write:space.permission:confluence, read:content.restriction:confluence, write:content.restriction:confluence, read:confluence-user, read:user:confluence.
• storage:app: keep the state of operations, described above, in Forge storage.
• report:personal-data: report to Atlassian every week the accounts whose identifier the app keeps.

Authentication

Calls to Confluence use the user's identity whenever they display something, and the app's identity for the copy itself, once permissions have been checked. The app holds no credentials of its own: there is no API token, no password and no secret to leak.

Encryption

The data the app keeps is held in Forge hosted storage, which Atlassian encrypts in transit and at rest under the Atlassian cloud data encryption policies. Exchanges with Confluence go through the Forge platform and never pass through a server run by the publisher.

Vulnerability management

Before every release, the code is scanned with Atlassian's Forge Security Requirements Tester and the dependencies with npm audit; findings are fixed before the release ships, and dependencies are kept up to date.

A vulnerability reported through the Atlassian Marketplace security program or by email is fixed within the timelines of the Atlassian Marketplace security bug fix policy. In case of a security incident or a critical vulnerability, customers and Atlassian are notified.