On Fri, 11 Jan 2008 14:23:54 -0800, firstname.lastname@example.org wrote: > IP: 126.96.36.199 > > Can I not set specific permissions on individual folders within the folders created via the Thecus interface?
Depending on the actual organisation of what you want to do a -very- simplistic solution would be: -to create your root directory e.g. SERVER using the TheCus web UI -to create additional directories each one corresponding to a grouping policy e.g. ADMINISTRATORS, DEVELOPERS, SUPER_USERS and USERS and with the ACLs you allocate for instance: *ADMINISTRATORS can be accessed only by ADMINs *DEVELOPERS can be accessed by ADMINs and DVPRs *SUPER_USERS can be accessed by ADMINs & DVPRs and SUs *and so on -then to create the same directory structure in all these directories -I am a bit excessive here but that's just for the sake of a short presentation -finally: when you want to filter user access then link your directory to another one in the corresponding folder of the policy you want to apply on the files -OK, you've to do the symbolic links manually. By applying the links properly, you'll be able to reproduce a convenient way to browse back and forth across the directories.
For instance -I don't mention ADMINs who can access everything: SERVER/ARCHIVES can only be accessed by SUs SERVER/DOCUMENTATION/PRODUCTS can be accessed by all USERs SERVER/DOCUMENTATION/PRODUCTS/BETA PRODUCTS can be accessed by only DVPRs SERVER/DOCUMENTATION/PRODUCTS/BETA PRODUCTS/MARKETING can be accessed by DVPRs and SUs
so, you'll have links like: ARCHIVES in SERVER -> ARCHIVES in SUPER_USERS PRODUCTS in DOCUMENTATION -> DOCUMENTATION in USERS BETA PRODUCTS in PRODUCTS -> BETA PRODUCTS in DEVELOPERS MARKETING in BETA PRODUCTS -> MARKETING in SUPER_USERS but MARKETING should also be accessible from a higher level in the SUPER_USERS
The SERVER directory is just there as a policy-neutral entry point, it has no real use beyond that.
I apologize for daring mentioning such a primitive method!