Forum Discussion
Preservation Lock Settings for Labels
I am working with labels as a replacement to retention in SharePoint Online. To meet the 17-4a SEC rule I need to enable preservation lock. There are different policies to meet for 5, 7, 10, Forever retention with delete after the date is reached. I dont see the Preservation Lock setting when creating the policies, but when I go into edit them it starts to load and then disappears. Is this a bug, is it by design, is it a feature that is coming, or is it just not going to be possible.
I do not see the ability to edit the labels and policies after I have created them, which I suppose is in effect a lock of sorts since I have the labels to be marked as a record. I do see the options and can edit policies that are created via retention in the data governance.
It's by design. Labels don't have the "lock" option, it's configured on the policy, and only when creating it.
Seems like an odd way to do it. I can closely correlate labels to SharePoint content types, just without the metadata. This is great for flagging content and marking them as records instead of relying on SharePoints old way, which consequently doesnt work very well in online unless you are doing inplace records.
Our original approach was going to be to send files to a records center based on an information policy and that site collection have a policy with preservation lock, but that move does not appear to work appropriately. Since I can apply both retention and deletion to a label and mark that item as a record to me it would make sense to be able to apply a preservation lock on the label since it is in effect a policy. Now when I go to create the policy container for all my labels I dont get preservation lock, which does make sense because not all of my labels may need to have preservation lock. It appears that the only way to do the preservation lock is via data governance > retention, which would then be one site collection per retention period more or less since I cant search against additional fields yet and the query editor wont necessarily ensure I am getting the right documents. One site collection per time period is tough to sell because of the user experience for end users. For instance a department may have many different types of record types with different retention periods, having them jump between site collections is not a good experience.
Well, keep in mind that Labels and in general the whole data governance suite is targetted at multple workloads, not just SharePoint. The Exchange folks have expressed similar concerns about some of the changed (lacking) functionality.
