I don’t wanna See all Site Content
Recently I came accross a instance where the user did not want to see the View All Site content link above the quick links. Can’t blame him. After making the UI look as business friendly as possible, clicking on the View All Site Content would spit out a list of document libraries and lists categorized according to the technical implementation, very useful for a site administrator, but making no sense to the average business user.
So I decided to put in a bit of security trimming in the masterpage. By default the View All Site Content link is within the tag <Sharepoint:SPSecurityTrimmedControl runat=”server” PermissionsString=”ViewFormPages”> meaning that as long as Tom Jones has the permission to view form pages, he would he would view this link. Changing the PermissionString attribute to ManageWeb solved this problem, thus making sure that only the Admin could see this.
So what are the other valid options for PermissionString? Here they are thanks to Zac Smith who got them out from a reflected SharePoint DLL
List Permissions
ManageLists
CancelCheckout
AddListItems
EditListItems
DeleteListItems
ViewListItems
ApproveItems
OpenItems
ViewVersions
DeleteVersions
CreateAlerts
ViewFormPages
Site Permissions
ManagePermissions
ViewUsageData
ManageSubwebs
ManageWeb
AddAndCustomizePages
ApplyThemeAndBorder
ApplyStyleSheets
CreateGroups
BrowseDirectories
CreateSSCSite
ViewPages
EnumeratePermissions
BrowseUserInfo
ManageAlerts
UseRemoteAPIs
UseClientIntegration
Open
EditMyUserInfo
Personal Permissions
ManagePersonalViews
AddDelPrivateWebParts
UpdatePersonalWebParts
So how do I determine which groups have these permissions? Simple; Go to Site Permissions and on the settings button select permission levels
Select on the group for which you want to check the permission level and there it is.
Finally a tool for creating BDC App definiton files
This seems to be long over due. After all reading the hype that MS puts around BDC its a disappointment once a person tries to implement it and realize that he would have to write out a huge XML file to get it working. Not very nice.
One had to rely on a third party tool called BDC Meta Man to help generate the file, which was a tad bit expensive for the professional version $1200.Now the latest version of MOSS SDK comes with a BDC Definition editor tool. More details here. Wonder what BDC Meta Man will do now? Slash prices and improve features? Or throw down the towel and fade into oblivion.
Can’t wait to check out the new BDC tool.
