Deprecated: YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container::__construct(): Implicitly marking parameter $parameterBag as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php on line 60

Deprecated: YoastSEO_Vendor\League\OAuth2\Client\Provider\AbstractProvider::authorize(): Implicitly marking parameter $redirectHandler as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/league/oauth2-client/src/Provider/AbstractProvider.php on line 416

Deprecated: YoastSEO_Vendor\GuzzleHttp\Client::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/Client.php on line 181

Deprecated: YoastSEO_Vendor\GuzzleHttp\ClientInterface::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/ClientInterface.php on line 77
{"id":747,"date":"2012-01-30T14:19:34","date_gmt":"2012-01-30T13:19:34","guid":{"rendered":"https:\/\/blog.sharedove.com\/adisjugo\/?p=747"},"modified":"2012-01-30T14:19:34","modified_gmt":"2012-01-30T13:19:34","slug":"editing-the-limited-access-permission-level","status":"publish","type":"post","link":"https:\/\/blog.sharedove.com\/adisjugo\/index.php\/2012\/01\/30\/editing-the-limited-access-permission-level\/","title":{"rendered":"Editing the “Limited Access” permission level"},"content":{"rendered":"

I had a question today, being asked if one can modify the "Limited Access" permission level in SharePoint 2010. The goal was to remove the "Browse User Information" permission from the "Limited Access" level.<\/p>\n

<\/p>\n

Without taking responsibility for the mess the code will produce $\"Winking$ , like not being able to pick users from the user picker control, yes, it is possible to do it through the Object Model, the snippet is fairly simple:<\/p>\n

<\/p>\n

\n\/\/get the limited access permission level from the web\nSPRoleDefinition limitedAccessRole = web.RoleDefinitions["Limited Access"];\n\n\/\/get the permissions associated with this permission level\nSPBasePermissions limitedAccessPermissions = limitedAccessRole.BasePermissions;\n\n\/\/remove the "Browse User Information" permission from the permissions\nlimitedAccessPermissions = limitedAccessPermissions ^ SPBasePermissions.BrowseUserInfo;\n\n\/\/assign the permissions again to the "Limited Access" permision level\nlimitedAccessRole.BasePermissions = limitedAccessPermissions;\n\n\/\/update\nlimitedAccessRole.Update();\n<\/pre>\nAgain, please do this on your own responsibility<\/u><\/strong>, "Full access" and "Limited Access" are not made "read only" in the SharePoint user interface without a good reason.<\/p>\n
\n\t\t\t  \n\t\t\t  <\/div><\/div>\n\t\t