Migration of consent
Only relevant when using the Individual Access (OAuth 2.0) authentication method.
See Authentication methods
What is "migration of consent"?
Files from private git repositories have to be shared by someone who has access to that file. Once that is done, the git file can be viewed in Confluence as long as that user has access to the file.
Someone leaving your organisation is a primary example of when someone loses access to files in git.
You want to consider migrating all consent given by a user before removing a user from your git organisation or you will result in the scenario shown below.
Timo has shared a file to which he has access.
Timo no longer has access to the file in your git organisation.
Migration of consent allows you to quickly share all files of this specific user on your behalf instead.
Perform a migration
Navigate to settings in Confluence
In the menu on the left side you can find the menu item "Git for Confluence Administration" under the section "Administration".
Navigate to the tab "Shared files" to view all git files that have been shared on all pages across your Confluence instance.
On this page you can filter the results by one or more users. Select one or more shared git files to get the option to transfer the consent to your self.
