This is version 1 2 3 4 5 6 7 8 9 . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Information on the different protocols: VFS_Protocols
#

Below this is the setup for the user's virtual file system (VFS). The left side has a list of directories you can browse that represent your local machines hard drives and servers. This is the "Server's Files". Double click on an item to open it. Use the drop down menu to go back up a level. In general, you will only use this list if you are connected with remote administration. You can drag items from this left side over to the right side which is the users VFS. So for instance, I could drag "Crush" over to the right. On Windows, mapped network drives won't work when running as a service. Its a feature of the OS. Here is the workaround.

In the VFS, I have added the single item named "Crush" which is a hard drive on my system. If I double click on it, you will see the real contents of it and their types will be either "DIR" or "FILE". You may also right click on items in this list to edit their properties. This VFS area supports drag and drop from the left side of the user manager. This makes it extremely easy to just drop a folder and the user now has access to it.

The items to the right are the permissions for the selected item. I have given full access to the folder "ftp_testing". Most of the permissions are self explanatory. The resume permission allows users to resume a transfer, either upload or download. Slideshow allows users to view a slideshow of image thumbnails. Share allows users to right click and share items with other people. Invisible makes an item "hidden" from the users view. If you tell them its there though, they can still access it by typing in the path to it manually. To remove access to an item completely, you need to make it invisible, and turn off all other options. Free ratio allows for the same sort of function, but it refers to if you have a ratio set. And finally Quota is a integer value for how many MegaBytes the user has available for this directory. A quota is only calculated based on files that come in and out of the CrushFTP server if you do not enable the RealFile Quota option.

The "Inherit / Reset" button removes any custom settings on the selected item, and makes it inherit its permissions from its parent.

If you want to control access for items contained inside the root item, you may do so. Browse to a folder you want to change the access on, and click the appropriate access for it. You cannot change the names on real items or get properties on them. You can however change their permissions. You'll notice on the right side the options are gray. This is because the item selected (software) is inheriting its setting from the parent item. If I change a checkbox here, then the items will no longer be gray as its not inheriting anymore. If you want to go back to inheriting, click the "Inherit / Reset" button.

---

VFS Linking
This allows you to take a VFS configured on other users, and have it merged into the current user. So you may have defined certain folder access on template type users, and you can make other users use those VFS settings. Any changes made to the original user's VFS are then applied to users who are linked to that VFS.
This allows not just linking in one VFS, but multiple VFSs. This is a different concept from inheritance as inheritance replaces the user's VFS with another user's VFS. VFS linking lets you have a custom VFS for the user, plus add in other items from other VFSs.

An example:

user1 inherits from group1. user2 inherits from group1 and group2.

group1 has basefolder, which has various items in it. group2 has folder2 which has various folders in it.

When user1 or user2 logs in, you want them to see the contents of basefolder and the contents of folder2...at their root level.

What you do is on group1, you add basefolder to the user's VFS. Then right click and virtually rename it and call it "user_home". Set permissions on that. You set group1 to have VFS linking back to group1. (Circular VFS link.)

Now on group2, you add folder2 to the user's VFS and virtually rename it to be called "user_home". Set permissions on that. You set group2 to have VFS linking to group2. (Circular VFS link.)

When user 1 inherits from group1, they get the VFS linking telling hem to link to group1's VFS...therefore getting user_home folder. When user2 inherits from group1 and group2, they get the VFS linking telling hem to link to group1's VFS and group2's VFS...therefore getting user_home folder...twice, merged together. This is called VFS colliding. You collided two different VFS's together to make one merged VFS for the folder named "user_home".

When either user logs in, at their / folder they are seeing the contents of "user_home".