Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

Would like to not inherit permissions when adding subfolder
Last Post 11/24/2014 2:24 PM by Peter Donker. 4 Replies.
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Kate
New Member
New Member
Posts:29


--
10/29/2012 8:48 PM
We have a root folder that is accessible to more than a thousand security groups, and each security group has it's own proprietary folder below the root that only that security group can see. We had to set it up that way for menu reasons.

However, I would like to be able to add a new subfolder( that doesn't inherit the permissions of the parent folder. The parent folder does NOT have Unify Permissions on Children selected BTW.) Right now when we add a new folder we have to uncheck the rights of 1,000 security groups (and we could always miss one).


FYI:DocX (version 6.0.3) and installed it on DNN community version 6.01.05. DNN is resident on a hosted server. We set up DocX to use Lucene Search provider.


Peter Donker
Veteran Member
Veteran Member
Posts:4530


--
10/31/2012 10:01 AM
I can't see how you can do this. It is kind of inherent in your setup. If this is a regularly recurring task you could contemplate creating a custom module to do the folder creation. There are consultants in the DNN ecosystem who could make something like that for you.

Peter
Rob Ralston
Basic Member
Basic Member
Posts:164


--
11/01/2012 11:28 AM
I was thinking there might be a of way to accomplish this with much less work.

First, have the security role "Registered Users" with "View" permission at the top level folder, or if that is a concern, create a new security role called "All DMX Users" and give it "View" permissions at the top level folder. You would need to add all DMX users to this role as well as their own proprietary role.

Remove permissions from all the other proprietary roles at the top level folder.

Now, when you add a new proprietary folder, you should only have to deal with two roles:
a) remove permissions for the "Registered users" or "All DMX Users" role since it would be inherited.
b) add permissions for the new associated proprietary security role to the new proprietary folder.

As a reminder, never run "Unify Permissions" from the top level folder since it would overwrite all your settings in the proprietary folders. Note: "Unify Permissions" is a one time operation you can trigger when needed on a given folder.

Hope this makes sense and helps.

Rob Ralston
stehtimschilf
New Member
New Member
Posts:8


--
11/10/2014 10:52 AM
Hi
I know, this post is almost 3 years old and I'm running into the same problem.
Question to the DNN-Team: Wouldn't it be easily to add a new Folder-Attribute: "inherit permissions"? If checked, all newly created sub items (folder, files) inherit the parent folder permission, while unchecked all new objects have no permissions?

cheerioh
Sven Gschwend
Peter Donker
Veteran Member
Veteran Member
Posts:4530


--
11/24/2014 2:24 PM
The fact is that this remains a fringe case. I mean: it is only an issue when you have lots of roles to uncheck. By default this is how all file systems work, however. I need to balance adding a setting to the confusion it may create. This is why I don't chase every single possible option out there. The danger is that users get too confused by all the options. Having said that: I'm not deaf to your plight. Maybe I could see something like a portal wide setting for it.

Peter
You are not authorized to post a reply.