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":74,"date":"2008-06-13T16:27:00","date_gmt":"2008-06-13T15:27:00","guid":{"rendered":"https:\/\/blog.sharedove.com\/adisjugo\/index.php\/2010\/11\/17\/working-with-user-roles-and-permissions-in-sharepoint-object-model-part-2\/"},"modified":"2008-06-13T16:27:00","modified_gmt":"2008-06-13T15:27:00","slug":"working-with-user-roles-and-permissions-in-sharepoint-object-model-part-2","status":"publish","type":"post","link":"https:\/\/blog.sharedove.com\/adisjugo\/index.php\/2008\/06\/13\/working-with-user-roles-and-permissions-in-sharepoint-object-model-part-2\/","title":{"rendered":"Working with user roles and permissions in SharePoint Object Model – part 2"},"content":{"rendered":"

In my previous post<\/a>, I have explained how to work with user roles and permissions in SharePoint object model, how to access and create SPGroup objects (SharePoint groups) on the fly, and how to assign Permission Leves (a.k.a Role Definitions) to these SPGroup (or SPUser) objects.<\/p>\n

Ok, but, what if existing, predefined Permission levels (Full Control, Design, Manage Hierarchy, Approve, Contribute, Read, Restricted Read, Limited Access, View Only) are not enough?<\/p>\n

You can always create your own Premission Level (Role Definition), and specify it’s rights by using SPBasePermissions enumerator:<\/p>\n

<\/p>\n

SPRoleDefinition newRole = new SPRoleDefinition();\nnewRole.Name = "Test FB Role Definition";\nnewRole.Description = "Description of new role definition";\nnewRole.BasePermissions = \n    SPBasePermissions.ViewListItems |\n    SPBasePermissions.Open |\n    SPBasePermissions.OpenItems;\n\nm_SharePointWeb.RoleDefinitions.Add(newRole);<\/pre>\n
By looking at the Permission Levels in our SharePoint site we see then our new Permission Level listed among the other (predefined level).<\/p>\n
\"image_2\"<\/a><\/p>\n
 <\/p>\n
And, to delete an existing role definition:<\/p>\n
m_SharePointWeb.RoleDefinitions.Delete("Test FB Role Definition");<\/pre>\n
Asigning this new permission level to a SPGroup would look like:<\/p>\n
SPRoleDefinition groupRoleDefinition = \n    m_SharePointWeb.RoleDefinitions["Test FB Role Definition"];\n\ngroup2RoleAssigment.RoleDefinitionBindings.Add(groupRoleDefinition);\n\nfolderTest2.Item.RoleAssignments.Add(group2RoleAssigment);<\/pre>\n
\n\t\t\t  
\n\t\t\t  <\/div><\/div>\n\t\t