Hi,

I have created a role to handle the settings of a module. I created the user and assigned him the role. Now, I went to the page where the module is, and modified the permissions to allow this role to "Manage settings". When I log in as that user, I can´t manage settings.

I don´t know what might be going on. When I allow that specific user to "manage settings" I can handle the module settings, but if I grant permissions to the role, I can´t.

Please let me know if you might have a clue about this.

Thanks!!

Do I understand that the permissions are set exactly the same for a user and for a role, but a user in the role can't manage the module settings?

1- I created a role A
2- I created a user DC and assigned the role
3- I went to the page where I have the module. As superuser, I assign the "manage settings" permission to this role and "Add content" permission.
4- I logged in as user DC. I can "Edit content" but can't edit settings.

5- I logged in as superuser and again, modify the permissions settings of this module. I granted the role "Full control"
6- I logged in as user DC. I can "Edit content" but can't edit settings.

7- I again logged in as superuser. I went to the module settings and assign the settings to the person, and not to the role. First, just "Edit content" and "Manage settings" permissions
8- I logged in as user DC. I can "Edit content" but can't edit settings.

9. I logged in as superuser, modify the permissions. For user DC I granted "Full Control"
10- Again, nothing

11. Finally, I went to page's settings and modify the permissions . I select for the role > view, add, add content and manage settings.
12. I logged in as user DC. now I can manage settings, but I'm not sure if this is because I have permissions as the user or as the role. So, I'll remove the user from the module's permissions and test again.

I can still edit settings.

So, summary, this is what I had to do :

1. Assign permissions to the page , and for the role, select "Add content", "view" and "Manage settings" control.

Now, this makes all the modules on the page have the "edit settings" available. And I didn't want this to happen. So I had to check one by one to remove the settings for those modules, for the role. But this doesn't work. So I had to hide the module for this role, as if I just unselect the "Manage settings"  for that role, it still does not work. But if I mark the "view" option as not available, it does.


So, basically, what I need is to be able to handle settings per module, for roles. And I can't do this.

The "Add content" permission works perfectly, but with this issue >

I don't need to select "manage settings" so as to be able to manage settings, by selecting "add content" at the page level, I can manage settings. This is also something it shouldn't happen.



Thanks,

Dana

I don't have access to a Pro installation of DotNetNuke at the moment, so I cannot test, but I think that you have described the situation correctly.  Giving permissions on the module lets you edit the module, or do other configuration that is internal to the module.  Adjusting the module level settings  is actually a page function!  That is why you need to give page edit permissions.

Oliver Hine (oliverhine.com) has a beta version of an advanced permissions provider, mainly aimed at adding the granular permissions present in DotNetNuke Pro to the Community Edition.  As persmissions is now a "provider" I believe that  opens the possibility of creating a provider that would do what you want.

I'll try to do some more looking at this one.