Group management

## Overview

Rendering nodes can be managed through groups. When accessing an application, you can specify a `groupId` parameter in the URL to route tasks to rendering nodes within that group. The system will intelligently schedule tasks to nodes in the specified group.

**Example URL with group parameter:**
```
http://192.168.0.50:8181/enterAppli?appliId=819163084126945280&groupId=816351359270912000
```

> **Note:** A `groupId` specified in the URL takes precedence over the group assigned during application creation.

The system includes a built-in **default group** that cannot be deleted. Tasks assigned to the default group can be handled by any rendering node.

## Adding a Group

Click the **Add** button to open the dialog, then fill in the group name, idle timeout, and workspace, then click **Save**.

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

- **Idle Timeout:** The period of inactivity (in seconds) before a user is automatically logged out when accessing via this group's URL. For example, setting this to 10 seconds means the user is logged out after 10 seconds of no activity.
- **Workspace:** Assigns a workspace to the group, which controls user management permissions for that group.

## Binding Rendering Nodes

Click the **Bind Rendering Nodes** button to open the binding dialog. From here you can bind or unbind nodes from the group.

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

- Nodes already bound to the current group will show an **Unbind** option.
- Nodes not yet bound to the group will show a **Bind** option.
- A node already bound to another group can still be re-bound to the current group by clicking **Bind**.