You are viewing limited content. For full access, please sign in.

Question

Question

Using TRM, allow users to create shortcuts only?

asked on July 10, 2015

Hey there,

 

We are using TRM, so users only see shortcuts to documents.  Sometimes they would like to copy a shortcut to another location in the repository, and I'd like to allow this but I don't want them also being able to create documents in that area as documents are stored in another location in the repository which has retentions and such setup and are managed via an import workflow process.  If I give users the ability to 'create documents' which seems to be necessary for creating shortcuts, they also can create documents.  Can I specify that an area can only contain shortcuts or somehow only limit them to being able to create shortcuts?  

 

Alternatively I was thinking of using a workflow process to create the shortcut for them via a business process or something similar, but I need to have a wait to prompt them for where they want it to go - which doesn't seem to be possible unless I'm missing something.  It would be incredibly handy if I could pop up a box that asked for a repository path to copy the shortcut to.

 

Any ideas?

 

-Shaun

 

0 0

Replies

replied on July 15, 2015

You are correct, the ‘create documents’ access right will give your users the ability to create documents and shortcuts. You will not be able to restrict that access right such that users would only be able to create shortcuts in that sense.

You could have workflow monitor an area that documents are stored in and give your users the ‘create documents’ right in that area. That workflow could be set up to delete entry when any new document is created. Configure your starting rule to monitor that set area for any new document created. This would still give your users the ability to create shortcuts and save you and/or your administrators the time of manually monitoring the folders for any newly created documents. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.