Currently, it is possible to open locked down Royal Document via the Powershell Module. However, could the ability to create a locked down Royal Document be added to the Powershell Module?
This would allow read only Royal Documents to be created and distributed.
Copied reply from a support ticket:
unfortunately it's currently not possible to create locked down document files using our PowerShell API. However you can open locked down files using PowerShell, and also manage them by providing the lockdown password to the "Open-RoyalDocument" cmdlet. Please notice that it's only possible to open locked down files at all when you know the lockdown password too.
To set up the encryption, without Lockdown, you can use the "Set-RoyalDocumentPassword" cmdlet.
Nick Reese
Currently, it is possible to open locked down Royal Document via the Powershell Module. However, could the ability to create a locked down Royal Document be added to the Powershell Module?
This would allow read only Royal Documents to be created and distributed.
Copied reply from a support ticket:
unfortunately it's currently not possible to create locked down document files using our PowerShell API. However you can open locked down files using PowerShell, and also manage them by providing the lockdown password to the "Open-RoyalDocument" cmdlet. Please notice that it's only possible to open locked down files at all when you know the lockdown password too.
To set up the encryption, without Lockdown, you can use the "Set-RoyalDocumentPassword" cmdlet.
1 person likes this idea