This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

CrushFTP-specific terms used in this wiki, and related:

Groups

a logical way to organize user accounts, our term for an Organizational Unit equivalent.

Inheritance

a way to automatically apply user settings from one user to another. The term roots in object oriented programming, there is a separate wiki on this

Group Template account

inheritance parent or archtype account, that parents inheritance for a group of user accounts

VFS Linking

loosely related to inheritance, a pointer to a VFS directory of another user account, there is a separate wiki on this

Groups in the user manager are a way to organize users into different lists. A group by itself does not imply any inheritance of settings. So a typical group will just organize users into a list, but there are no inheritance settings.

If you want groups and inheritance to work together, then you need to make a user who has the same name as the group, but not member of the group; we call this the Group template account. Be careful to keep the case on the username and group name the same.

For example, if you make a user name "events_for_upload", and make a group named "events_for_upload" as well, when you add users to this group, they will also be set to inherit settings from the user "events_for_upload". So it does both. But if the user "events_for_upload" did not exist, its only a list of users with no inheritance.

Using this you could configure events on the user "events_for_upload", and then everyone you add into the group would get these settings.

Modifying any inheritable settings on the Group Template user will automatically reflect on the inheriting ( group member) users. This makes bulk changes on multiple user accounts easy, by only editing one.