Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Is there a way to code/configure or utilise a 3rd-party solution that will enable per-document information management policies?

I have a client requirement whereby they require separate policies "per document". Per-folder or per-content type simply won't do. The process is this:

  1. User creates document
  2. User fills metadata
  3. Event handler fires and based on metadata, a new information management policy is configured

My current thinking is custom workflow is the only way to accomplish the goal as per-document policies are not OOTB.

share|improve this question
add comment

1 Answer

up vote 1 down vote accepted

Something might be able to be hashed out if you can branch out the documents into child content types. Perhaps if things are uploaded as a parent content type, then based on the the metadata provided, a workflow could set the content type to the proper child content type and would enforce the IRM policy.

If you think about it, IRM is working on a per document basis, since each document is subject to IRM. You'd just have to figure out what the retention policies for those documents are, create the proper parent and child content types, and configure a workflow to set things appropriately and let IRM do it's thing.

share|improve this answer
    
Not really the answer I was hoping to get (I wanted a magical answer which provided exactly what I was looking for). However, absent any other suggestions, the above is the most correct (i.e. let the workflow sort it out). Ultimately I think insisting on per-document IRM is the wrong approach. –  Neil Richards May 23 '11 at 21:48
    
Well, not all documents would or should have the same IRM policies, some should stick around longer than others. The only way to do that reliably is to use multiple content types. –  PirateEric May 23 '11 at 23:49
    
Multiple content-types do go a long way to helping IRM but one CT per document is unmanageable. I suppose it depends upon the use case. Ultimately it seems SharePoint wont support per-item IRM without code/some third-party solution. Thanks for the help. –  Neil Richards May 24 '11 at 6:17
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.