In the previous SharePoint version of SharePoint you couldn't have permissions on list views. Is this now possible on SharePoint Foundation 2010?
So for example I have a list and 2 views but I want to assign permissions to the views so that a user can see view A but not view B.
Also is it possible now to easily set permissions to items instead of having to click each item and assign permissions?
If you're comfortable with a little development, you could achieve this by:
Make both your views (I'll call them 'Boy' and 'Girl') hidden. I did this recently in CAML, but you probably could use the object model.
Create an application page to redirect users from this new page to the appropriate view. You can implement your own business logic here, however you want. Note that when redirecting, you'll need to make sure your GUIDs are upper case. Also, throw an exception if they don't have rights to either view.
Add a link to your redirection page to your navigation, so that users can be redirected.
Now, this solution isn't perfect - it prevents users from seeing the existence of the view(s) to which they lack rights, but doesn't stop the view from working if they type in the correct URL.
I guess a final step would be to add a control or some code to the pages for the Boy and Girl views to check the same business logic as the redirection, and if the user lacks rights to see that page, throws an exception. However, this does not secure the individual items against viewing - but I doubt you can achieve that without simply applying Item level permissions against items on your list.
You cannot set permission to views. There are new workflow actions for SharePoint Designer that could ease the per-item permission assignments via workflows. Check this blog post for some ideas, you could create some conditions to assign proper permissions.
Another thing you can do is create web part pages in SharePoint Designer that have Data View Web Parts on them. You can then set permissions on those pages or on the entire library where they reside.
I am not a developer, but I inserted webparts on several web pages. I then targeted the audience of each web part. If a user clicks on the link to the web page where they are not designated as part of the target audience, they do not see the web part. I was worried that someone would click on the title link to the source list that appears above the web part and accidentally get access to all data. To resolve this, I went to the source list page, used edit page to edit that web part and designate a target audience. Because users were creating data on their individual web parts (views) of the list, they needed to have editing rights based on the source list. So they have editing rights but are unable to view areas outside of the web parts where they have been included in a target audience. The tool was to collect budget data. The budget manager gets all his data in one file at the end that he can export to Excel.
I would like to understand why you would do all this work to make a web part that is viewable by only a few users where all users can see the content, if the content has not been granted unique permissions. What is the requirement?
Also, I have, for SharePoint 2010, lately been seeing lots of permissions issues where customers are setting unique permissions on multiple folders within a library which is causing a lot of problems in the resultant views. (Anecdotal evidence to be true.) Space is cheap. I would recommend creating new libraries (and lists) for each group of content permissions. Heck, new sub-sites, if possible. The trade-off is that you have to manage the permissions, but if the users wants unique permissions on content, probably better if he manages the permissions. Usually doesn't happen that way, but worth a try.
Just create a page and add a List view web part - in 2013 this is just insert -> Web Part -> select library. You can customize the view on this page and then set permissions to this page.
Don't use audience targeting as mentioned above as this isn't security. SharePoint is security trimmed, so if you add the page to the quick launch, if a user doesn't have access, he wont see it. Just make sure you add it as a heading and not a link.
