Migration Focus Area | Feature | Platform |
|
---|
Server | Cloud |
---|
Versioning/License | Version Support | | |
License | | Info |
---|
Monthly subscriptions are the default option, however, discounted annual subscriptions are available upon request to our Atlassian Sales team. |
|
Confluence Differences
| Creating a new Secured macro | Image RemovedImage Added | Image RemovedImage Added |
Decrypting the Secured macro | | |
Integration with other macros | Expand |
---|
title | Example of how Security and Encryption macros are nested with other macros... |
---|
| Image RemovedImage Added |
| Note |
---|
Due to this limitation, pages that contain Security and Encryption macros nested with other macros (such as the one highlighted for Server column on the left side) will fail to be migrated to Cloud. We suggest moving the Security and Encryption macros outside of the nested macros in server before performing the migration to Cloud. Feel free to contact our support team to get further advice about this. |
|
Other functions | An access log of each macro | Centralized view of all secrets on a space Centralized audit log of all macros on a space |
Macro Differences Overview | Server Macros | Cloud Macros |
This table lists the differences between Server/Data Center app and the Cloud version. | Secure | Secret |
Secure macro ownership CAN BE transferred the user who creates the Secure macro (creator) will always be the owner of the secret this ownership can never be changed to anyone, but, Confluence administrators have the privilege to modify the access settings of the Secure macro.
| Secret macro ownership CANNOT be transferred the creator of the Secret will be the owner of the secret by default, but they can add more owners. Subsequently, this means that the creator of the Secret can also be removed from the owner's field a Secret will always be tied to at least one owner Confluence admins in Cloud do not have the privilege to access these secrets unless they're the owner
Info |
---|
When a Group Owner member creates or edits a secret, they will be automatically added as a User Owner of the secret. |
|