Permissions Restriction in SharePoint 2010 Document Library

I recently created a Document Library in SharePoint 2010 so team members can upload their individual weekly reports. Is there a way I can set this Library up so each person who uploads their weekly report can only see their own report and no one else's? I know I could modify the permissions on each document individually after upload but that would be inefficient and tedious.

Is there a permissions functionality within SharePoint I could utilize or any method that doesn't involve code or a 3rd application?
Lord_DragonAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jamie McAllister MVPSharePoint ConsultantCommented:
There's a series of unsatisfactory hacks to achieve this, or a slightly different approach I'd prefer (option 2);

Option 1

Create a default view filtered on "Created By = [Me]"

Change permissions on the library so that ordinary users cannot create personal views or edit the main view

Switch off search indexing in the library settings

If you can, get one of the many sandbox solutions online and upload it, that will hide the "Open with Explorer" button on the ribbon

At this stage, you're in the position to deter most attempts. You let it be known that Auditing is enabled and tampering is not allowed.

Users will be unable to access other reports in general, but could still hack their way in with a URL (or by guessing a url) but once again you use auditing and code of conduct to head that off.

Not watertight but a 95% solution to the issue

btw you would never want to have item level permissions on all documents. Permissions do not scale well and can lead to all sorts of performance nightmares.

Option 2

The other way, is organize permissions on a container level. Therefore you create a folder per person and secure that with permissions. Each person can only add or view within their own folder. Permissions are set just once in this model.

Administrator can create views that ignore folders therefore have a holistic view of the reports. Views get security trimmed so others wouldn't see the content in others folders even using that view.

You need to police that people don't put folders in the root of the library. This can be policy, or you make access to the library Read Only, but access to the folder for that person as edit so their folder is the only place they can add a document.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Lord_DragonAuthor Commented:
Man, you're like the Yoda of SharePoint, that's was just the insight I needed. Thank you Jamie
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.