Manage Organizations¶

As an instance administrator, you have additional privileges compared to an organization administrator. You can not only manage existing organizations, but also create new ones, assign resources to them, and define global constraints.

Accessing the Interface¶

From the side panel, click on the Organizations menu. In instance administrator mode, additional options appear in the interface compared to a regular organization administrator.

Organization List¶

The Organizations page displays all organizations within the instance. Each row contains the following key information:

Organization name
Maximum number of machines/containers allowed
Status (active or inactive)
Studio Key for associating with desktops and containers
Creation date

A filter allows you to display only active or inactive organizations.

../../_static/images/instance/organizations/instance_orga_list.png — *List of organizations*¶

Creating an Organization¶

As an instance admin, you can create a new organization. Click the New Organization button, then fill in the required fields.

../../_static/images/instance/organizations/instance_orga_create.png — *Creating an organization*¶

The available configuration sections are:

General Information¶

Name: Full name of the organization.
Short Name: Short name, used in the custom login URL.
Connectors: Option to disable access to instance connectors on this organization’s login page.

Features¶

Enable Computers: Enables remote desktop management.
Enable Containers: Enables container management.
Enable Studio API: Allows the use of the Studio API for this organization.
Enable Cloud Providers: Allows linking cloud providers.

Licenses¶

You can limit the number of licenses consumable by the organization:

Remote Desktop Limit: maximum allowed for remote desktops.
Containers Limit: maximum allowed for containers.

Container Placement Constraints¶

You can define placement rules (constraints) for containers.

Important

These constraints will apply to all container profiles of the organization. If constraints are set here, they can no longer be modified in container profiles.

Status¶

Active: organization is immediately usable.
Inactive: suspended, with no access to resources.

Overview¶

The Overview page of an organization provides a summary of licenses in use and the general status of resources (users, remote desktops, containers). From this view, you can monitor in real time:

The number of Remote Desktop licenses consumed.
The number of Container licenses consumed.
The status of users (disabled, assigned).
The status of resources (desktops online, busy, or offline).

../../_static/images/instance/organizations/instance_orga_interface_as_admin.png — *Organization overview*¶

Important

From the organization view, you also have access to menus reserved for instance administrators. These pages allow you to associate instance-level resources such as container providers, images, and relays created at the instance level.

Advanced Usage¶

Instance admins retain full control over the quotas allocated to organizations.
Organization admins then manage their internal resources (users, container profiles, collections, etc.), but cannot exceed the limits set at the instance level.
The private key generated when creating an organization is essential for associating agents (computers, containers).
If necessary, you can modify quotas at any time or temporarily deactivate an organization.

Note

Internal management of the organization (users, desktops, containers, etc.) works the same way as for an organization administrator. Please refer to the corresponding documentation for details.