Referring to my earlier post – Restructuring-the-tridion-blueprinting-and-content-demotion – one of the issue while doing demote is the fact that you will loose any custom permissions you may have on your folders or structure group if the item successfully demoted.
To manage a track of what all folders have a custom permission and provide a list of pre and post demote report of custom permissions on all demoted folder, we at Content Bloom have created a core service script.
As a first step in this massive demote operation, we executed this script to gather a report of all custom permissions on every folder in the hierarchy.
When the demote process is completed, we executed this script again on the same folder in the new publication where the folder has been demoted.
The two reports are then compared to find missing custom permissions, which can then be setup back on each folder in the new publication where the folders have been demoted.
Below are few screen shots showing the script in action as well as the report generated in the form of a CSV: