Forum Discussion
Add protection to a sensitivity label - What happens to already labeled files?
Hi,
Lets say that we have already labeled several files with a basic sensitivity label does not apply encryption/protection. Then after labeling all these files for the last few weeks, we go back to the Office 365 SCC console and modify this sensitivity label to apply encryption.
What will happen with the files that were already labeled before this change? When will these files be protected and by how will th?
Thanks for clarifying.
Hello Chuck99. That is a good question. If the file was labeled without protection and you later add protection to the label the file will still have the label settings that were set at the time you labeled the file. It will not be updated because you later add protection to it.
- Pål WintherIron Contributor
Hello Chuck99. That is a good question. If the file was labeled without protection and you later add protection to the label the file will still have the label settings that were set at the time you labeled the file. It will not be updated because you later add protection to it.
- Chuck99Brass Contributor
Pål Winther TY for that information which makes a lot of sense.
On another note, I did change the label of a file from a label with protection (Highly Confidential - All employees) to a General label without protection. Even though the General was now applied to the file, the RMS protection behind seems to stay. I had to go in the protection settings (In Excel: File - Info - Protect Workbook - Restrict) to remove the protection.
Is that by design?
Thanks
- Pål WintherIron Contributor
Chuck99How did you change the label? With the client? Or via the bar/sensitivity button in Office? I just had to test it here to see if I could reproduce this so I protected a document with Highly confidential and saved. Then I closed/opened the document and changed to Public (without protection). I provided as Justification that the previous label no longer applied and saved my document with the new label. Closed/opened and it was labeled Public. So, maybe you experienced a bug? Can you try again to see if you get the same behaviour?