cancel
Showing results for 
Search instead for 
Did you mean: 

Restricting Users

mattsmith
Champ in-the-making
Champ in-the-making
Hi All,

I would like to remove some of the options from within a folder inside of a site, I'd like to remove options such as "move to" and "copy to". These are to be removed only on certain folders from within the sites document library and only to a specific group of people.  Could anyone advise on the best way to achieve this? 

Many Thanks
Matt
4 REPLIES 4

mikeh
Star Contributor
Star Contributor
Using the web-extension mechanism, override documentlist.get.config.xml and add permission attributes to the CopyTo and MoveTo actions, e.g. permission="matt-permission". If there's one already there, comma-separate it, e.g. "delete, matt-permission"

Then, on the Repository side, override the webscript helper library slingshot/documentlibrary/evaluator.lib.js, look for the SPECIFIC TO: FOLDER section and add your business logic there to decide who should get permissions["matt-permission"] = true to enable the actions.

Thanks,
Mike

soborno
Champ in-the-making
Champ in-the-making
Thanks, I was looking for that too, and it work like a charm!
But I notice that the "actions" that appear on the right side of folders, in the folder structure, are not affected by the changes at documentlist.get.config.xml. Anyone knows how to do that.

Regards
Claudio

mikeh
Star Contributor
Star Contributor
Thanks, I was looking for that too, and it work like a charm!
But I notice that the "actions" that appear on the right side of folders, in the folder structure, are not affected by the changes at documentlist.get.config.xml. Anyone knows how to do that.
Yes they are, but they're in a different action set in the config file.

Note, you'll also have to update document-actions.get.config.xml and folder-actions.config.xml respectively to reflect the changes on the details pages.

Thanks,
Mike

soborno
Champ in-the-making
Champ in-the-making
Yes they are, but they're in a different action set in the config file.

Note, you'll also have to update document-actions.get.config.xml and folder-actions.config.xml respectively to reflect the changes on the details pages.

Thanks,
Mike
As you said, it works perfectly now!
Note, the file is folder-actions.get.config.xml

Thanks
Claudio