Container Management

Containers allow users to run isolated environments (e.g. secure browsing sessions or specific applications). They are based on Container Profiles that define their configuration and rules.

Important

This feature is available starting with the Enterprise plan.

It requires the Reemo Containers licensing model.

Container Profiles

Container Profiles act as templates. They define the image, constraints, and options applied to generated containers.

Profile List

Overview of available container profiles.

The Container Profiles page lists all container profiles defined in the organization. Each row in the table shows the following information:

• Name: the name of the Container Profile.

• Container Provider: the infrastructure used to run the container (e.g. Reemo SWARM1).

• Image: the base image used (e.g. Chromium).

• Expire after: the expiration period of the container after disconnection.

• Managing Group: the group managing this profile, if defined.

• Created At: creation date and time of the profile.

This view provides a quick overview of which profiles are available, their basic configuration, and governance status.

Create a New Profile

1. Go to the Container Profiles menu.

2. Click New Container Profile.

3. Fill in the information:

   • Provider and Image (required)

   • Name (profile name)

   • Expiration: delay after disconnection to automatically stop the container

   • Clipboard restrictions: enable/disable read and write

   • Custom Icon (SVG) (optional)

   • Constraints: placement rules (e.g. location)

   • Options: options of the deployed image

Note

These options depend on the selected image and are determined by the instance administrator managing deployed images.

Container profile creation screen.

Edit a Profile

You can edit an existing profile to adjust its settings (name, expiration, constraints, advanced options).

Editing a container profile with options and constraints.

Assign Users to a Profile

Users must be associated with a Container Profile to be able to launch containers.

1. Open the container profile.

2. Click Assign users.

3. Select the users and confirm.

User assignment window for a profile.

Profile View

Information of a container profile (name, image, expiration, provider, managing group).

A Container Profile page displays the following information:

• Name: profile name.

• Image: image used to run the container (e.g. Chromium).

• Container Provider: the infrastructure where containers of this profile will be created (e.g. Reemo SWARM1).

• Expire after: maximum lifetime of a container after disconnection.

• Managing Group: group administratively responsible for the profile (if defined).

• Usage Schedule: usage schedule applied to the profile (default: None = unlimited).

• Created At: profile creation date and time.

From this page you can:

• Edit the profile settings (name, image, constraints, advanced options, etc.).

• Assign users to the profile.

• Delete the profile from the organization if needed.

An additional tab shows users associated with this Container Profile.

Container profile with assigned user.

Containers

Once Container Profiles are configured and assigned, users can launch containers. Each container corresponds to a running instance, visible in the Containers section.

Container List

Overview of active or stopped containers.

The columns display:

• Name and Hostname

• OS and version

• IP

• Status (Online, Offline, Busy)

• Profile used

• Associated collection (if applicable)

• Owner user

• Creation date

Container Profile

Container information (OS, status, user, associated profile, activity logs).

Container Collections

Collections allow grouping multiple Container Profiles and assigning them to a set of users. They make it easier to manage standardized environments (e.g. “Internet Navigation”, “DevOps”, etc.).

Collection List

Overview of existing collections.

The Collections page shows all collections in the organization in table format. Each row corresponds to a collection and contains the following columns:

• Name: collection name (e.g. Internet Navigation, DevOps).

• Identifier: unique identifier of the collection, used for integrations or SSO mapping.

• Managing Group: the group responsible for the collection (if defined). Administrators of this group can modify the collection.

• Created At: collection creation date.

From this view you can:

• Click on a collection to access its detailed view (information, Container Profiles, and associated users).

• Create a new collection via the New Collection button.

Create a Collection

To create a new collection:

Collection creation form.

Fill in:

• Name: collection name

• Identifiers: additional identifiers (SSO mapping)

• Managing Group: managing group (optional)

Once the form is completed, click Create.

Collection Profile

Main information of a collection.

From this profile, you can manage:

• Assigned Container Profiles

• Assigned users

• Deletion of the collection

Assign Container Profiles to a Collection

A Collection does not directly contain containers but Container Profiles. By assigning one or more profiles to a Collection, you define which environments are available to users associated with that Collection.

1. Open the profile of the desired Collection.

2. Click on the Container Profiles tab.

3. Press the Assign container profiles button.

Selection window for adding Container Profiles to a Collection.

4. Select one or more Container Profiles from the list.

5. Click Assign to confirm.

The chosen Container Profiles now appear in the Collection’s Container Profiles tab. They are displayed with their main information (name, image, provider, expiration, etc.).

Container Profiles successfully assigned to a Collection.

• A user must be assigned to a Collection to access the Container Profiles included in it.

• Access rights and options remain those defined in the original Container Profile.

• You can assign or remove Container Profiles from a Collection at any time.

Assign Users to a Collection

A Collection must be associated with users to grant them access to the Container Profiles it contains. Without this step, the container profiles included in the Collection will not be available to users.

1. Open the profile of the desired Collection.

2. Click on the Users tab.

3. Press the Assign users button.

User assignment window for a Collection.

4. Select one or more users from the list.

5. Click Assign to confirm your choice.

6. Close the window with Done.

The selected users now appear in the Collection’s Users tab.

Collection view with assigned users.

• A user can belong to multiple Collections.

• The user’s access rights depend on the Container Profiles included in each Collection.

• Removing a user from a Collection automatically revokes their access to the related Container Profiles.

Containers Created from a Collection

When users launch a container from a collection, it appears in the Containers tab.

Active container created from a collection.

Summary

Container management is based on two main concepts:

• Container Profiles: A container profile defines the configuration of a container (image, constraints, options, restrictions). It can be directly assigned to users to provide them with a specific environment.

• Collections: A collection groups one or more container profiles and allows them to be assigned to a set of users. This simplifies centralized management of standardized environments (e.g. “Internet Navigation”, “DevOps”, etc.).

In summary:

• Use Container Profiles if you want to create and assign environments individually (one profile = one specific configuration).

• Use Collections if you want to manage sets of environments and distribute them easily to multiple users.