Group management

The rendering nodes can be managed through grouping. When accessing the application on the web, users can set the groupId parameter by constructing the URL, for example: http://192.168.0.50:8181/enterAppli?appliId=819163084126945280&groupId=816351359270912000. The system will intelligently schedule tasks to rendering nodes under the same group. Additionally, when creating an application, users can specify the application's group. It's important to note that the parameter specifying the group takes precedence over the selected group for the application.

The system has a built-in default group that cannot be deleted. If the groupId corresponds to the default group, tasks can be assigned to all rendering nodes. Rendering nodes can be bound to different groups.

When adding a group, users can click the "Add" button, which will prompt a dialog to enter the group name and idle timeout, select a workspace, and then click "Save" to successfully add a group.

- Idle Timeout: Setting the group's idle timeout to 10 seconds. When accessing the application through a URL constructed with this group, if there is no activity within ten seconds, the user will be automatically logged out.

- Workspace: Selecting a specified workspace allows for setting user management permissions for the group.

Clicking the "Bind Rendering Nodes" button will open a dialog to bind nodes to a specific group. Nodes already bound to the current group can be "Unbind," while nodes not yet bound to that group can be "Bind."

If a rendering node is already bound to another group, it can still be re-bound to the current group by simply clicking "Bind."

Images:

![](https://docs.paraverse.cc/media/202504/2d2dae241a16479cb2b870e23d4ac1842406.png)

![](https://docs.paraverse.cc/media/202504/e3e7dd1019c445b38ac4fdfa41d029057717.png)