Control access to subfolders

[bobwolfson]

I have a folder containing other folders, one per user.

I want to share the subfolders to the users via HFS.  Is there an easier way to do this than to individually drag each subfolder into HFS as a real folder (at the top level), create an account for each user, and then tie the individual accounts to the corresponding individual folders?

It would be slightly nicer to drag the parent folder into HFS and then be able to tie accounts to its subfolders, but there doesn't seem to be a way to associate accounts with subfolders of a real folder.  Am I missing something?

[bmartino1]

re add the same folder to a public share that is acessible to the users

[bobwolfson]

I really don't understand what you're trying to tell me.

Let's say I have a folder, in Windows, called "MainFolder".  Within it I have subfolders: "Cust1Folder", "Cust2Folder",...

Let's say in HFS I have accounts for Cust1, Cust2,... and I want Cust1 to only be able to access/upload to Cust1Folder, Cust2 to only access/upload to Cust2Folder, etc.

Now, I know I can do this by adding Cust1Folder, Cust2Folder, etc. individually to HFS, and then setting permissions on each one.

I also know I can just put MainFolder in HFS and set each account's "After ~login redirect to" attribute to their appropriate subfolder.  However, that doesn't stop an account from navigating up a level after login and seeing all the other accounts' folders.

It would be nice if HFS had the concept of a "root folder" per account, like FTP - i.e. a way to limit an account to navigating no higher than a particular folder in a hierarchy.

Does anything like that exist?  Could it be added?  Would anyone be interested in adding it (for a fee)?

[bmartino1]

bind to rot option will need to be enabled...
Mars and other user would be of better help here

[rejetto]

the process you described is correct, and the only way to make it quicker is to make a little script.
There are scripting commands for creating folders, adding folders, creating users, setting permissions, etc.
http://www.rejetto.com/wiki/index.php?title=HFS:_scripting_commands#Virtual_File_System_manipulation

You can make a protected page, with a form, and the script to process the form.
The standard template already uses this kind of mechanism, passing form data to server-side scripts.
The only extra step is to put all this in a folder, and restrict access to that folder.

There's no "individual root" at the moment, sorry, and i'm personally not available in this period.