Client groups
Organize worker clients into teams and visibility scopes.
Organize worker clients into teams and visibility scopes.
This screen belongs to the Router deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.
Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.
Step-by-step actions
- Click Groups → Create group.
- Enter docs-team and select private.
- Click Create, refresh and locate the new group.
- Assign workers through the supported client connection/API of your installation.
Every control and its meaning
| Control / parameter | Values, units and effect |
|---|---|
| Название / Name | Required group name, for example docs-team. This is a worker organization object. |
| Видимость / Visibility | private, tenant or public. Choose the required visibility; this does not replace server-side tenant authorization. |
| Состав / Members | The list shows client count. The current creation form edits name and visibility and has no client-assignment editor. |
Verify the result
Verify visibility as the intended member. An empty group does not prove execution isolation.
Errors, disabling and reverting changes
Cancel discards the unsaved form. Deleting the group removes its record but leaves workers intact; review associations before confirmation.
2026-10-15 · Actual staging application and an existing operator session. Synthetic data or non-personal configuration only; credentials and the operator profile are excluded. A form alone does not establish persistence or replica consistency.
- Name
- Private
- Create
Detailed security settings · Traffic analysis · FAQ · All application sections