Group is abstract set of users, which gives assigned users some permissions. So it is not necessary to specify permission for each single user.
There are independent levels of permissions implemented in CloverETL Server
permissions to Read/Write/eXecute in sandboxes - sandbox owner can specify different permissions for different groups. See Sandbox Security and Permissions for details.
permissions to perform some operation - user with operation permission "Permission assignment" may assign specific permission to existing groups.
permissions to launch specific service - see Chapter 15, Launch Service for details.
Table 4.3. Default groups created during installation
| Group name | Description |
|---|---|
| admins | This group has operation permission "all" assigned, which means, that it has unlimited permission. Default user "clover" is assigned to this group, which makes him administrator. |
| all users | Every single CloverETL user is assigned to this group by default. It is possible to remove user from this group, but it is not a recommended approach. This group is useful for some permissions to sandbox or some operation, which you would like to make accessible for all users without exceptions. |
Relation between users and groups is N:M. Thus in the same way, how groups are assignable to users, users are assignable to groups.
Groups permissions are structured as tree, where permissions are inherited from root to leafs. Thus if some permission (tree node) is enabled (blue dot), all permissions in sub tree are automatically enabled (white dot). Permissions with red cross are disabled.
Thus for "admin" group just "all" permission is assigned, every single permission in sub tree is assigned automatically.