Setting item level permissions was straight forward in SharePoint 2010, you selected the items you wanted to break inheritance on and selected the Permissions item. When moving to SharePoint 2013 and trying to do the same thing, to a lot of users this functionality appears to no longer exist. Worry not!
To set item level permissions for an item (or multiple items) select the candidate items and switch to the Items tab in the ribbon.
Notice the ribbon item called Shared With. This is what replaces the Permissions item from 2010. Click it and a list of users that the item is shared with loads.
If you’re working on a SharePoint solution that requires a custom code access security (CAS) policy, the following is an easy way of determining the permission(s) you need to add to the config.
For this to work, you need to be able to debug the code, which should be a given, considering you’re creating a custom CAS for a solution you’re writing . 🙂
A basic CAS will look something like:
<permissionset class="NamedPermissionSet" version="1">
<ipermission class="SecurityPermission" version="1" Flags="Execution"></ipermission>
<ipermission class="AspNetHostingPermission" version="1" Level="Minimal"></ipermission>
<ipermission class="Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=126.96.36.199, Culture=neutral, PublicKeyToken=71e9bce111e9429c" version="1" ObjectModel="True"></ipermission>
<assembly Name="$SharePoint.Project.AssemblyName$" Version="$SharePoint.Project.AssemblyVersion$" PublicKeyBlob="$SharePoint.Project.AssemblyPublicKeyBlob$"></assembly>