Scroll Content Manager is migrating from Atlassian Connect to Atlassian Forge to improve security, reliability, and align with Atlassian's Cloud platform. This migration does not change how you use Scroll Content Manager, but you may notice minor interface differences and updates with new releases.
The documented changes are a result of the migration to Atlassian Forge and reflect current platform capabilities and limitations. We continue to work with Atlassian's evolving platform and will make improvements as Atlassian expands Forge capabilities.
What's Changing
Not much will change for you as a user, the migration mostly affects what happens behind the scenes. You'll notice a few small differences in the interface, described below.
Larger interface elements
Some dialogs and buttons may appear larger than before. This is due to current limitations in Forge UI resizing capabilities, which prevent us from matching the exact dimensions of the previous Connect-based interface. This only affects the visual appearance and the functionality remains the same.
Bookmarks may need to be updated
URLs within the app are changing as part of the migration. If you've bookmarked links to specific views, such as the version list of a document, those bookmarks won't work after the migration. You'll need to save the new URLs.
Do I Need to Do Anything?
No action is needed on your part.
Migration to Forge Timeline
We’re committed to migrate to Forge fully before the end of 2026. For specifics on the timeline for Scroll Content Manager and other K15t apps, please refer to Forge Transition Timeline.