The Scroll Documents conversion tool offers a number of conversion options in addition to the general content selection based on versions, variants or languages. This article will teach you about these options and how they affect conversion results.
Copy Space Permissions
By default, when you generate a space in Scroll Documents, it's only visible to you, the converting user. This gives you a private playground to test the conversion tool without other Confluence users peeking in.
If you want to change that, you can check the "Copy Space Permissions" option. This means the generated space will inherit all the same permissions as the original space managed by Scroll Versions or Translations. It's a handy option if you want to maintain your existing access settings.
Initially, avoid copying space permissions for early tests to keep the space private. However, during the actual conversion, we recommend enabling this option. If not, you'll have to set permissions manually afterward.
Copy Inline Comments
By default, inline comments don't get migrated over to your new Scroll Document.
But if you check this box, all your inline comments will be copied over to the generated Scroll Document. Keep in mind though, if you're working with versioned spaces, inline comments might be duplicated if you have pages that belong to multiple versions in Scroll Documents. This can affect unversioned and fallback pages too.
To prevent duplicated inline comments across multiple versions, avoid checking this option during conversion.
Preserve Inline Conditional Content
Scroll Documents already supports paragraph-level conditional content in Confluence Cloud. But if you were using inline conditional content macros in Scroll Versions, you should anticipate some changes.
By default, the conversion tool will convert all your Scroll Versions conditional content macros to the equivalent Scroll Documents macros. However, it might cause some line breaks that you weren't expecting, especially if you had inline conditional content macros in your content. This is also mentioned in: Conversion with Conditional Content
Convert Page Keys
Scroll Versions assigns page keys to pages. When you convert, these page keys become Context Keys in Scroll Documents. They work quite similarly, but with a twist – you can use them in Scroll Viewport, but not within the Confluence UI.
Conclusion and Next Steps
That's a wrap on these advanced conversion options. Now you're armed with the knowledge to make the right choices when converting your content with Scroll Documents.
Whether you want to copy permissions, include inline comments, preserve inline conditional content, or convert with page keys, you can tailor the conversion to suit your needs. Just remember to consider how these options might impact your content and workflow.
Head back to Convert a Space to Scroll Documents to follow the last steps in your conversion journey. Happy converting!