CODEWITHSUNDEEP
sensenet
Luciano Valinho
Luciano Valinho

Reputation: 59

Configuring roles permissions on sites in Sensenet

I am having trouble configuring my site permissions on sensenet. I create an role with users on it. I have a site, with the default document library. On permissions of the site I added as security entry an role with all permissions. But the users that belong to this role, doesn't have access to all features like "upload files" of the document library. I can see the content but I cannot make actions.

If I give all permissions to this role it is supposed to have the same permissions as admin user to this site, right?

Here's the permission of the site:

permission of the site

Upvotes: 0

Views: 112

Answers (1)

Miklós Tóth
Miklós Tóth

Reputation: 1511

My guess is that the role does not have 'Run application' permission for the necessary applications.

In Sense/Net permissions have two sides:

  1. permissions on the content itself, for example on the site or library (that is what you have, it looks correct).

    This is what determines which content can the user access and the 'level' of the access too. For example See permission means you can see that the content is there but cannot do much with it. Open gives you access to all data (but only read it), Save lets you modify it, etc. But as you can see, these permissions are relatively general, they are not related to specific features (although you can define your own custom permissions for your needs, but that is not necessary in most cases).

  2. permissions on actions/applications

    This is the other side: what can the user do with the content, which actions are accessible to him? In Sense/Net there is an application content for every action (e.g. Upload, see below). There are many of these and it should be possible to specify which action is executable by the user and which one is not. This is what the 'Run application' permission is for. So besides having permission on the content (in your case the site or library) you have to give Run application permission for the user or group on the necessary applications.

For example to make these features 'clickable', grant 'Run application' permission (it is at the bottom of the checkbox list) on these applications for your group:

  • Upload button: /Root/(apps)/Folder/Upload
  • Access the Edit page: /Root/(apps)/GenericContent/Edit
  • Modify permissions: /Root/(apps)/GenericContent/SetPermissions

See more details here: Permission settings in production

(let us know if you do not find the application for the feature you want them to access - sometimes the application is not in the global 'apps' folder as in these examples, but under a lower level 'apps' folder, e.g. under the site)

Upvotes: 1

Related Questions