2

Is there a way to set permissions on a folder in a document library - let's call it a Confidential folder - such that anyone can view the list of files in the folder but only authorised people can view/open/download them?

I have tried to use the in-built "View" permission level and it does not meet my requirement (it still allows the user to view and download).

Code/non-code solutions are invited.

I'm aware this question has been asked previously but I haven't seen an answer to it.

Improve this question
9
  • have you tried limited access permission level?
    – Waqas Sarwar MVP ♦
    Feb 18, 2015 at 12:59
  • Is Limited Access actually a permission level? How can I use it to meet my requirements?
    – Submits
    Feb 18, 2015 at 13:06
  • You want to restirct the user to view only but not open. that what i think may be work in your conditions. becuase this one dont have open item in it.
    – Waqas Sarwar MVP ♦
    Feb 18, 2015 at 13:08
  • The built-in "View only" permission level also does not have "Open" permissions but users are still able to open files in the document library.
    – Submits
    Feb 18, 2015 at 13:13
  • this one also does nto have the view items permission as well. SO best is try.
    – Waqas Sarwar MVP ♦
    Feb 18, 2015 at 13:14

2 Answers 2

Reset to default
0

Try creating a group to put users in. When you create a group there are options for the different levels of permissions. One of the options is a restricted read. This may give you what you are looking for. It's at least worth a try.

Improve this answer
1
  • Tried it - didn't work. The problem is the Restricted Read has the "View Items" permission assigned to it (which has this description: "View items in lists, documents in document libraries, and view Web discussion comments.") With this permission assigned users can see documents in a library AND open them in the browser (but not download them).
    – Submits
    Feb 18, 2015 at 16:03
0

In the end I got around this issue by having permissions at item level rather than folder level.

Originally, permission inheritance was being broken on the folder and all files in the folder were inheriting permissions from the folder.

Now, the folder inherits permissions from its parent (the list) and the files within the folder all have inheritance broken on them with unique permissions on each one.

This allows me to give read/edit permissions to only the files in the folder that I choose. This is actually achieved with an event receiver. When someone uploads a file into this folder, the event receiver breaks inheritance on it immediately and gives read/edit permissions to the uploader. The uploader can then manually go in and give permissions to any further people they want to share the file with.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

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