# UserManagerAdminRestricted

**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](Groups.md)** 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](Inheritance.md)** on this

**Group Template account**\
inheritance parent or archetype account, a user account that is named exactly as the group, acting inheritance parent for a group of user accounts. In case of a Restricted Admin scenario, sets the per-group confinement directory.

**VFS Linking**\
loosely related to inheritance, a pointer to a VFS directory of another user account, there is a separate **[wiki](VFS.md)** 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](Groups.md)** with the corresponding **Group Template** account, a user account that is named exactly as the group, and not member of the group itself. The Group Template User 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.

**IMPORTANT !** A user can act as Group Template Account if and only if it's username matches exactly the group name. Manually forced inheritance does not make the inheritance parent account a Group Template Account. The two ways relationship is based on the matching username-group name.

**11.2.3_15+** Supports **[Connection Profiles Limited Admin](Connection-Profiles-Limited-Admin.md)** at User Manager too. Using Connection Profiles the Restricted Admin can assign remote locations to the group members.

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.

### Setup Roles And Groups

tab

<img src="UserManagerAdminRestricted/admin_restricted_base.jpg" width="1440" alt="Admin restricted base">

### Roles Panel

tab

<img src="UserManagerAdminRestricted/admin_restricted_roles.jpg" width="475" height="480" alt="Admin restricted roles">

### Permissions Panel

tab

<img src="UserManagerAdminRestricted/admin_restricted_permissions.jpg" width="476" height="480" alt="Admin restricted permissions">

Since CrushFTP **v10** we now support multiple groups for the same admin. Each group has to have designated it's own Group Template account, and the VFS directories assigned to these need also to be granted to the Restricted Admin, or this latter to be pointed to an upper-level directory.\
With the Restricted Admin scenario functional:\
1.) If the user is not a member of the group, the change is rejected.\
2.) If the home folders being specified are not a subfolder of the home directory that the group user can access, the change is rejected.\
3.) If the change involves adding an event to a user that specifies a "plugin" action, the change is rejected.\
4.) Other admin escalation permissions are denied too.\
These are done to enforce security and prevent privilege escalation. Any attempted violation is logged in the server log for audit purposes.

---

Finally, the view from a limited admin when they log in. Please note the group selector in the top-center area.

<img src="UserManagerAdminRestricted/admin_restricted_view.jpg" width="1440" alt="Admin restricted view">

These are done to enforce security and prevent privilege escalation.
