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 . 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. There is a separate wiki on this

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

---

An administrator can can delegate administration allowing a limited administrator to create and manage users in their group, and assign folders that they themselves have access to. We'd call this administrator a Restricted Admin account.

First need to create a user Group with the corresponding Group Template account. This latter is to be assigned some top level VFS directory under which the group member users will have their own working directories later on. The same VFS is to be granted to the Restricted Admin, these two settings together will confine both the admin and the group members under that directory, with no escalation possible.

Then grant the admin on the Setup Roles panel the Remote User Only Administration (Limited) role permission, the group name to administer, and eventually restrict the admin roles even further on the Setup Permissions ( limited admin only) panel.

The user manager will only contain a list of users who are part of a group that matches their username exactly. So if test2 is a limited admin, there must be a group named "test2". The test2 group should not have test2 as a member, or else test2 can edit himself. At line 9 removed 6 lines So if test3 is a limited admin, there must be a group named "sub_admin" in my example. The sub_admin group should not have test3 as a member, or else test3 can edit themselves. There must also be a user named "sub_admin" which has a VFS with the folders you want the admin to be able to work with. At line 19 changed one line 2.) If the home folders being specified are not a sub folder of the home directory that the group user can access, the change is rejected. 2.) If the home folders being specified are not a sub folder of the home directory that the admin can access, the change is rejected. At line 23 changed 8 lines 4.) Other admin escalation permissions are denied too. These are done to enforce security and prevent privilege escalation. Any attempted violation of these is logged in the server log for audit purposes.

---

Finally the view from a limited admin when they login. These are done to enforce security and prevent privilege escalation.