Groups
Group is an abstract set of users, which gives assigned users some permissions. So it is not necessary to specify permissions for each single user.
There are independent levels of permissions implemented in CloverDX Server
-
permissions to Read/Write/eXecute in sandboxes - The sandbox owner can specify different permissions for different groups. For details, see Sandbox content security and permissions.
-
permissions to perform some operation - user with an operation permission Permission assignment may assign specific permission to existing groups.
-
permissions to launch specific service - For details, see Data Services.
| Group name | Description |
|---|---|
Administrator |
This group has an operation permission all assigned, which means that it has unlimited permissions. Default user clover is assigned to this group, which makes him administrator. |
Everyone |
A special group with auto-managed membership – it always includes all users, nobody can be removed. Once installed, the group cannot be deleted or renamed. By default, it has no permissions. It can be used to set the default permissions. |
All users |
This legacy group was intended to include all users; however, the assignment must be maintained by server administrator. If you really want to handle all users, use the Everyone group instead. It is possible to remove users from this group, but it is not recommended. This group is useful for some permissions to sandboxes or some operations which you would like to make accessible for all users. |
L2 support |
Members of the L2 support group have broad access permissions to CloverDX Server and can change many of its settings. The group is targeted at technical operators of the Server who need to solve various issues or who need to deploy new versions of code to the Server. |
L1 support |
Members of the L1 support group have limited access to CloverDX Server. The group is aimed at operators who help with basic Server maintenance – monitoring jobs, rerunning them, investigating production issues and so on. |
Job developer |
Members of the Job developer group have broad access to CloverDX Server. The group is aimed at non-production environments and is designed for users who need to develop and test CloverDX solutions. |
QA engineer |
Members of the QA engineer group have broad access to CloverDX Server. The group is aimed at non-production environments and is designed for users who need to develop and test CloverDX solutions. |
Data App users |
Members of the Data App users group have very limited permissions and can only access Data Apps user interface. Members of this group cannot access full CloverDX Server. |
Read-only users |
Members of the Read-only users group have very limited permissions. The group applies to users who need to monitor job execution on the Server or who want to see how the jobs work via Job Inspector. |
Wrangler |
Members of the Wrangler group have access to Wrangler user interface and can create and run Wrangler jobs. Members of this group cannot access full CloverDX Server Console. |
Users assignment
Relation between users and groups is N:M. Thus in the same way, how groups are assignable to users, users are assignable to groups.
| Any change in user assignment to groups will automatically log out the affected users from all their active sessions and force them to log in again. |
Group permissions
Group permissions are structured as a tree, where permissions are inherited from the 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 white cross are disabled.
Thus for the admin group just the all permission is assigned, every single permission in the sub tree is assigned automatically.
With none of the following privileges, a user can: log into the Server Console, create a server project (in Designer) from its own sandbox, create a file in its own existing sandbox, and run graphs.
| Any change in group permissions will automatically log out all users assigned to the affected group from all their active sessions and force them to log in again. |
-
The user with this permission has all available permissions. The Admin group has all permissions by default.
-
Allows the user to perform operations on all sandboxes, even if the sandbox accessibility is not specified explicitly.
This permission does not include the suspend sandbox permission.
-
Allows the user to work with sandboxes. This permission contains all the permissions below. The user can perform operations only on sandboxes owned by himself or on sandboxes with explicitly added access to him, see Sandboxes.
-
In the Server web interface, it allows the user to list their sandboxes and sandboxes with read permission granted to the user’s group.
In the Server web interface, this permission is necessary to create, edit, or delete sandboxes.
Within a sandbox with the write access granted, the user can edit or remove files and create or delete directories even without this permission.
-
Allows the user to create new sandboxes.
If a sandbox is to be created in web interface, the user must have the list sandbox permission.
-
Allows the user to delete sandboxes.
If a sandbox is to be deleted in web interface, the user must have the list sandbox permission.
-
Allows the user to edit sandboxes.
If a sandbox is to be modified in web interface, the user must have the list sandbox permission.
-
May delete files missing in uploaded ZIP
In , it allows the user to use a checkbox to delete files missing in the ZIP to be uploaded. If the user does not have this permission, the checkbox to delete mission files in ZIP is not displayed.
If a sandbox is to be uploaded from a ZIP file in the Server web interface, the user must have the list sandbox permission.
-
-
-
Allows the user to add and remove Libraries. No special permission is required to use them, all authenticated users may use public subgraphs from installed Libraries in CloverDX Designer.
-
Allows the user to manage schedules, see Scheduling.
-
Allows the user to list all schedules.
-
Allows the user to create new schedules.
The user must have the list schedule limited permission to access the scheduling section to create a new schedule.
-
Allows the user to delete schedules.
The user must have the list schedule limited permission or list schedule permission to access the scheduling section to delete the schedule.
-
Allows the user to edit schedules.
The user must have the list schedule limited permission or list schedule permission to access the scheduling section to edit the schedule.
-
-
Allows the user to manage event listeners, see Listeners.
-
Allows the user to list all event listeners.
-
List of Jobflow Event Listeners unlimited
Allows the user to list jobflow event listeners.
-
List of Graph Event Listeners unlimited
Allows the user to list all graph event listeners, see Graph Event Listeners.
-
List of File Event Listeners unlimited
Allows the user to list all file event listeners, see File Event Listeners (remote and local).
-
List of JMS Event Listeners unlimited
Allows the user to list all JMS listeners, see JMS Message Listeners.
-
List of Universal Event Listeners unlimited
Allows the user to list all universal event listeners, see Universal Event Listeners.
-
List of Task Event Listeners unlimited
Allows the user to list all task event listeners, see Task Failure Listeners.
-
-
Allows the user to create event listeners.
If an event listener is to be created in the Server web interface, the user must have permission to list the event listeners of the particular type.
-
Allows the user to create new Jobflow Event listeners.
If a Jobflow event listener is to be created in the Server web interface, the user must have the list of jobflow event listeners limited permission.
-
Allows the user to create graph event listeners.
If a graph event listener is to be created in the Server web interface, the user must have the list of graph event listeners limited permission.
-
Allows the user to create graph event listeners.
If a file event listener is to be created in the Server web interface, the user must have the list of file event listeners limited permission.
-
Allows the user to create JMS event listeners.
If a JMS event listener is to be created in the Server web interface, the user must have the list of JMS event listeners limited permission.
-
Create Universal Event Listener
Allows the user to create universal event listeners.
If a universal event listener is to be created in the Server web interface, the user must have the list of universal event listeners limited permission.
-
Allows the user to create task event listeners.
If a task event listener is to be created in the Server web interface, the user must have the list of task event listeners limited permission.
-
-
Allows the user to edit event listeners.
If an event listener is to be created in the Server web interface, the user must have permission to list event listener of the particular type.
-
Allows the user to edit jobflow event listeners.
If a jobflow event listener is to be edited in the Server web interface, the user must have the list of jobflow event listeners limited permission.
-
Allows the user to edit graph event listeners.
If a graph event listener is to be edited in the Server web interface, the user must have the list of graph event listeners limited permission.
-
Allows the user to edit file event listeners.
If a file event listener is to be edited in the Server web interface, the user must have the list of file event listeners limited permission.
-
Allows the user to edit JMS event listeners.
If a JMS event listener is to be edited in the Server web interface, the user must have the list of JMS event listeners limited permission.
-
Allows the user to edit universal event listeners.
If a universal event listener is to be edited in the Server web interface, user must have permission list of universal event listeners limited permission.
-
Allows the user to edit task event listeners.
If a task event listener is to be edited in the Server web interface, user must have permission list of task event listeners limited permission.
-
-
Allows the user to delete event listeners.
-
Allows the user to delete jobflow event listeners.
The user must have the delete graph event listener permission to delete a jobflow event listener.
It a jobflow event listener is to be deleted in the Server web interface, the user must have the list of jobflow event listeners limited permission
-
Allows the user to delete graph event listeners.
If a graph event listener is to be deleted in the Server web interface, the user must have the list of graph event listeners limited permission.
-
Allows the user to delete file event listeners.
The user must have the delete graph event listener permission to delete a file event listener.
If a file event listener is to be deleted in the Server web interface, the user must have the list of file event listeners limited permission.
-
Allows the user to delete JMS Event Listeners.
The user must have the delete graph event listener permission to delete a JMS event listener.
If a graph event listener is to be deleted in the Server web interface, the user must have the list of JMS event listeners limited permission.
-
Delete Universal Event Listener
Allows the user to delete universal event listeners.
The user must have the delete graph event listener permission to delete universal event listener.
If a universal event listener is to be deleted in the Server web interface, the user must have the list of universal event listeners limited permission.
-
Allows the user to delete task event listeners.
If a task event listener is to be deleted in the Server web interface, the user must have the list of task event listeners limited permission.
-
-
Allows the user to manually execute a task (send an email, execute a script, etc.) with an immediate effect.
-
-
Unlimited access to execution history
Allows the user to perform the same operations as unlimited access to execution history list permission.
-
Allows the user to view edge debug data in Job Inspector - Data Inspector panel in CloverDX Server and in the Data Inspector in CloverDX Designer.
-
Allows the user to access the Data service section, see Data Services.
-
-
Allows the user to access the Tasks history section, see Tasks.
-
Grants the user all its sub-permissions.
-
Allows the user to access the Monitoring section. For the Operations Dashboard, the List dashboards and monitors permission is also required.
See Monitoring.
-
Operations dashboard write access
Allows the user to create, edit and delete dashboards and monitors.
-
Allows the user to suspend the server, a Cluster node, or a sandbox.
The user must have the Monitoring UI permission to access the Monitoring section.
-
Allows the user to suspend or resume the server.
The user must have the Monitoring UI permission to access the Monitoring section.
-
Allows the user to suspend or resume a Cluster node.
The user must have the Monitoring UI permission to access the Monitoring section.
-
Allows the user to suspend a sandbox. The user must have list sandbox permission to view the sandboxes to suspend them.
See also Sandboxes.
-
-
Deprecated.
-
If the graph is to be run from server web interface, the user must have the list sandbox permission to list the graphs.
-
If the graph is to be run from server web interface, the user must have the list sandbox permission to list the graphs.
-
-
-
Allows the user to access the configuration section.
-
This permission allow user to access the Users section and configure user accounts.
-
Allows the user to list users and access to the Users administration section ()
-
Allows the user to change his password and to change password of another user.
To see list of users, the user needs the list user permission.
-
Allows the user to change group assignment.
To see the list of users, the user must have the list user permission.
-
Allows the user to change his profile (first name, last name, email, and password).
The user can access his/her profile in main web console view under username, in upper right corner of the page. See user profile for more information.
-
-
Allows the user to unlock a user.
The user must have the list user permission to list available users.
-
Allows the user to disable a user.
The user must have the list user permission to list available users.
-
Allows the user to create a new user.
If the user is to be created in the Server web interface, the creating user must have the list user permission to list users to access this option.
-
Allows the user to assign users to groups.
The user must have the edit user permission to successfully finish the assignment of users to groups.
If the user is to be created in the Server web interface, the creating user must have the list user permission to list users to access this option.
-
-
Allows the user to manage groups: user can list groups, create groups, delete groups, edit the group, assign users to the group, and change permissions of the group.
-
Allows the user to list groups. This permission is necessary for use of other options from the Groups group.
-
Allows the user to create a new user group.
If the user group is to be created in the Server web interface, the user must have the list groups permission to view a list of groups and to access this option.
-
Allows the user to delete a user group.
Only empty groups can be deleted. You need to have the list groups permission to view list of groups and to access this option.
-
This permission allow user to edit user groups.
This permission does not include User assignment and Permission assignment.
If the user group is to be edited from server web interface, the user must have the list groups permission.
-
Allows the user to assign users to groups.
The user needs Edit group permission to commit the changes in the assignment.
If the assignment is to be edited in the Server web interface, the user must have the list groups permission to list the groups.
-
Allows the user to configure group Permissions.
The user needs have the Edit group permission to commit the changes.
If the permissions are to be edited in the Server web interface, the user must have the list groups permission to list the groups.
-
-
Unlimited access to Secret Managers
Allows the user to create, edit and delete Secret Managers.
-
Allows the user to view System Info and CloverDX Info sections.
-
Allows the user to view Server Properties tab in CloverDX Info section.
The user must have the CloverDX/System info sections permission to access CloverDX Info section.
-
Allows the user to reload and view the server license.
The user must have the CloverDX/System info sections permission to access the Configuration section.
-
Allows the user to update the server license.
The user must have the CloverDX/System info sections permission to access the Configuration section.
See Activation.
-
Server Configuration Management
Allows the user to import and export the server configuration.
-
Allows the user to access Temp Space Management section.
-
Allows the user to access the server setup.
See Setup.
-
Allows the user to create a Thread dump and a Heap Memory Dump.
See Diagnostics.
-
-
Allows the user to run Groovy scripts.
-
Open Server Console
Allows the user to log into the Server Console.
-
Allows the user to log into the Wrangler UI console.