Moving to Forge

If you administer an Atlassian site with Snapshots installed, you may have seen a warning in Atlassian Administration, under Connected apps, telling you that an app runs on Connect and that Connect reaches end of support on 31 January 2027.

This page explains what that meant for Snapshots and for Access Agent, and what changed when they moved to Forge.

When the move happened

We moved Snapshots and Access Agent from Connect to Forge on Saturday 10 October 2026.

The move was automatic, and the apps request the same permissions as before. You did not need to do anything for the move to happen.

Your apps keep working

The warning was not a fault, and it was not a security incident. Snapshots and Access Agent may have been unavailable for a short time during the deployment window. Apart from that, they run normally, and your existing snapshots are unaffected.

Where our apps stand today

Connect is the Atlassian app framework that came before Forge. Atlassian is retiring it, and has started showing administrators which of their installed apps still run on it.

What changed after the move

Forge and Connect handle a few things differently, so some behavior changed after the move.

Snapshots User Settings has moved. On Connect, you opened your Snapshots user settings from your Confluence profile. On Forge, they are in the left sidebar: under Apps, select Snapshots User Settings. We will update Snapshots User Settings in this manual to point there.

Exporting to Excel. When you export a snapshot to Excel, a confirmation dialog now appears, telling you that the app is opening an external link to download the file. Confirm it to download the file. On Connect, the download started without this dialog.

Page history. After the move, a new page version created by taking a snapshot was recorded with the Snapshots app user as its author, and the comment "Updated snapshot by user name". Since version 4.10.0 (23 October 2026), a snapshot taken from the page is recorded under the person who took it again, with the comment "Updated snapshots", as on Connect. Snapshots taken by automation, or through the take-snapshot override, are recorded under the Snapshots app user.

Who can take a snapshot. After the move, the Take snapshot button was enabled only when both you and the Snapshots app had edit permission on the page. Since version 4.10.0 (23 October 2026), your own edit permission is enough again, as it was on Connect. This needed a small change to the app's access scopes (the manifest now sets allowImpersonation: true), rolled out automatically with nothing for you to approve or update.

The Snapshots app still needs its own edit access for snapshots taken by automation, and for groups an administrator has let take snapshots without edit access. For those pages, a space administrator needs to make sure Snapshots has permission to edit pages in the space, and, if a page has page-level restrictions, add Snapshots to the people who can edit it. See Permissions for snapshots.

Included pages in a space where Snapshots is disabled. A page in a space where Snapshots is disabled can include another page that contains snapshots. On Connect, those snapshots did not show. On Forge, page viewers who have view access to the included page see its snapshots. Page viewers without view access to the included page do not see the included page at all, snapshots included.

Links to external pages. When you click a link in the apps that leads outside your Atlassian site, such as a link to this manual, a dialog now appears first, telling you that you are about to leave the site. On Connect, the link opened directly.

Exporting large snapshots to PDF. Forge limits the content a macro can contribute to the Confluence PDF export to about 5 MB. To export pages with very large snapshots to PDF, use Scroll PDF Exporter instead of the Confluence PDF export.

Questions

Write to us at support@radbee.com. If you have a compliance or procurement deadline that depends on the migration, tell us and we will give you what we can.