Security Rights on folders & documents

[mohasinmujawar56]

When we are removing or assigning rights on folders for a particular user or role then we have an option to recursively apply it for child folders and documents (Parent to Child). But do we have any option to reverse it (Child to Parent)...?

For example, I have folder hierarchy like 'Folder A'-> 'Folder B'-> 'Folder C' -> 'Folder D' then I can do like if I assign rights for 'user A' to not to see 'Folder A' and I can apply it to 'Folder B' as well as to 'Folder C' by clicking checkbox saying 'recursively assign rights'. But if I want 'user A' to see a document in 'Folder D' and not other folders or documents then I have to first assign right for the folder to 'Folder A' then 'Folder B' then to 'Folder C and then to 'Folder D' and the document. Can we automate this like if I assign right to document then automatically it should apply to its parents. Like if I assign right to a document in 'Folder D' then the rights automatically gets assigned to 'Folder D' and its parents 'Folder C', 'Folder B', 'Folder A'...???

[jllort]

Your suggestion seems interesting, before response about it I must thinking on it for a while. Anyway, all depends on how you're setting security are several ways to get the same results. My suggestion is studio at the beginning the document types, who can access it, working with depts or abstract groups of users etc...

For example
ROLE_GENERAL, ROLE_A, ROLE_B
level1 -> ROLE_GENERAL ( general at root )
- level2.0 -> ROLE_A, ROLE_B
- level2.1 -> ROLE_B

level1 -> ROLE_A, ROLE_B
- level2.0 -> ROLE_A, ROLE_B
- level2.1 -> ROLE_B

On what will be OpenKM version 7, we've solved by document type based on file plan. ON 6.4 and below must be used more traditional way of setting grants ( like any OS ). In OS you can observe you can propagate privileges in deep, but not in way you're suggesting. Normally this things are for some reason and although your suggestion seems interesting I want to thinking on it about some possible bad cases.