SPSecurityTrimmedControl or "How to hide stuff from people"

Useful attributes of the control:
  • PermissionContext - against which user permissions will be tested
(possible values: CurrentSite, CurrentList, CurrentFolder, CurrentItem or RootSite)
  • PemissionMode - does the user have to meet all role definitions or just one of them
(possible values: All or Any)
  • PermissionsString - what permissions does the user need to see the content - can enter some values separated by comma
(possible values are from the enumeration SPBasePermissions:
EmptyMask,ViewListItems,AddListItems,EditListItems,DeleteListItems,ApproveItems,OpenItems,ViewVersions,
DeleteVersions,CancelCheckout,ManagePersonalViews,ManageLists,ViewFormPages,Open,ViewPages,
AddAndCustomizePages, ApplyThemeAndBorder,ApplyStyleSheets,ViewUsageData,CreateSSCSite,
ManageSubwebs,CreateGroups, ManagePermissions,BrowseDirectories,BrowseUserInfo,AddDelPrivateWebParts,
UpdatePersonalWebParts,ManageWeb, UseClientIntegration,UseRemoteAPIs,ManageAlerts,CreateAlerts,
EditMyUserInfo,EnumeratePermissions,FullMask)
  • AuthenticationRestrictions - allows to differ between authenticated and anonymous users
(possible values: AllUsers, AuthenticatedUsersOnly, AnonymousUsersOnly)
save, check-in, publish and there you go!

Ref link : https://www.infowisesolutions.com/blog/Comments.aspx?ArticleId=28

Comments

Post a Comment

Popular posts from this blog

How to remove app from SharePoint 2013/2016

I have installed an SharePoint App for creating surveys but when try to uninstall / remove it from the site it shows exception message " sorry we couldn't remove the app ". Solution: I have used following Power-Shell commands to install/remove app successfully  $instances = Get-SPAppInstance -Web <URL> $instance = $instances | where {$_.Title -eq '<app_title>'}   Uninstall-SPAppInstance -Identity $instance
Read more

The model backing the context has changed since the database was created. Consider using Code First Migrations to update the database

One way to resolve this error is to use Code First Migrations to update the database schema to match the new model. To do this, you can use the following steps: Open the Package Manager Console in Visual Studio by going to Tools -> NuGet Package Manager -> Package Manager Console. In the Package Manager Console, run the command Enable-Migrations to enable migrations in the project. Run the command Add-Migration <migration-name> to create a new migration for the changes you made to the model. Run the command Update-Database to apply the changes to the database.
Read more