What is COSU mode?

COSU, or Corporate Owned, Single Use, is a model intended for company-owned devices that are meant to serve one specific purpose. Unlike scenarios in which the user makes use of many device functions, here the smartphone or tablet operates in a highly restricted way and is dedicated to a single use case.

Most often, COSU mode is used when the device is intended to serve as:

• an information kiosk,
• a customer service terminal,
• a registration device,
• a check-in point,
• a screen with one or several selected applications.

In practice, this means that the organization not only manages the device, but also restricts access to system functions and prepares the working environment in such a way that the user can only use the intended scenario.

What does the video show?

In the video, we present the process of adding an Android device to Essentials MDM in COSU mode. The process begins in the administrative console, where the administrator selects the Android platform and COSU mode.

Next, the appropriate device group is selected. This is important because the assigned group determines which policy will be applied after deployment. In the example shown, the device is assigned to the COSU group and receives a configuration prepared specifically for the kiosk scenario.

On the device side, the process is carried out using a QR code. The device then goes through configuration and is automatically deployed into kiosk mode.

Adding a device in COSU mode – step by step

1. Starting the device addition process in the Essentials MDM console
   The process begins by creating a new device in the system. The administrator selects the option to add a device and then indicates:

• the Android platform,
• COSU mode.

The procedure itself is similar to other deployment scenarios, but already at this stage we define that the device will operate as hardware intended for a single purpose.

2. Selecting the device group
   The next step is assigning the device to the appropriate group – in this case, the group intended for COSU mode. This is a very important stage because the group affects the policy, settings, and applications that will be applied after deployment.

The system then shows what type of deployment will be carried out, which policy the device will be assigned to, and which elements will be applied automatically after registration is complete.

3. Generating the QR code
   After confirming the settings, Essentials MDM generates a QR code that will be used to start deployment on the device. This is a quick and convenient method, especially when the company is preparing a larger number of devices for a similar scenario.

The QR code makes it possible to connect the device to a previously prepared configuration without the need to manually apply many settings on the phone.

4. Preparing the device after a factory reset
   On the device side, a phone or tablet restored to factory settings is used. This is important because deployment in COSU mode takes place on a device prepared from the beginning to work in a specific scenario.

On the Android welcome screen, the QR code reader is launched by tapping the screen six times. Then the code generated earlier in the console is scanned.

5. Connecting to the network and starting configuration
   After scanning the QR code, the device asks to connect to a Wi-Fi network. Internet access is required in order to download the configuration and start deployment.

After entering the network details, the user goes through the basic Android setup wizard. At this stage, the standard first-start steps are performed, but after that the process begins to differ from other deployment models.

6. Automatic detection of the device by the system
   The video shows that Essentials MDM automatically detects that the QR code has been scanned. Thanks to this, the administrator can immediately see in the console that the device has been added and can check what stage the deployment process has reached.

This is important because from that moment on, it is already possible to monitor the progress of the configuration and preview the actions being performed by the system.

7. The biggest difference compared to COBO – full deployment before handing over control
   The most important difference between COSU and COBO is that in the COSU scenario, the device does not hand control over to the user until deployment has been fully completed.

This happens because the system still needs to configure kiosk mode. In practice, this means that the user cannot perform their own actions on the device or interrupt the process during this time. All steps are carried out automatically, and the device prepares the target work screen.

This is very important from the perspective of security and deployment consistency. Thanks to this, the device is handed over to the user already in a properly restricted and ready-to-use environment from the very beginning.

8. Kiosk mode configuration
   After the main stages of registration are completed, the device moves on to kiosk configuration. This is where the target screen and work environment are created, in which the user will have access only to the intended functions or applications.

In the material shown, the device completes configuration after some time and switches to the screen prepared earlier. This means that the most important deployment elements have already been applied.

9. Further app installation and finalization of configuration
   Although the main part of the configuration has been completed, some applications may still be installing in the background. This is visible both on the device and in the logs in the Essentials MDM console.

This is not a problem – the most important thing is that the device has been deployed correctly and is already operating in the appropriate mode. The remaining elements may be completed automatically after a short while.

10. Device restrictions in COSU mode
    After deployment is complete, the device already operates in COSU mode, which means that the user’s access to the system is heavily restricted. In the example shown, there is no access to the standard settings bar or typical system functions.

Only notifications and elements related to the operation of the device itself and app installation are visible. This clearly shows the nature of COSU mode – the device is not intended for general use, but for performing one specific task.

Why is COSU a practical deployment model?

COSU mode works well wherever predictability, ease of use, and full control over the device matter. The company can prepare the work environment in such a way that the user does not have access to unnecessary functions and uses only the elements required for a given scenario.

The main benefits of this approach are:

• reduced risk of user-side errors,
• greater control over the device,
• the ability to create a simple and consistent work environment,
• better security,
• convenient deployment of devices for specific tasks.

This solution is especially useful in service points, retail, logistics, receptions, registration desks, and anywhere a device is meant to function as a tool for one specific purpose.

What should you pay attention to when deploying COSU?

Although the process itself is simple, it is worth remembering a few practical points:

• the device should be restored to factory settings,
• it must have internet access,
• it is worth preparing the appropriate group and policy in advance,
• you need to take into account that the device will not hand over control to the user before configuration is fully completed,
• some applications may still be installing after the target kiosk screen is launched.

Thanks to this, the deployment runs smoothly and the final result is consistent with the intended usage scenario.

Summary

The video shows that adding a device in COSU mode in Essentials MDM is a structured and predictable process. The administrator prepares the configuration in the console, selects the device group, generates a QR code, and then starts deployment on the device after restoring it to factory settings.

After scanning the code, the device goes through configuration, is automatically recognized by the system, and deploys kiosk mode. Only after this process is complete does the user gain access to the ready-to-use work environment.

This is a practical solution for organizations that want to deploy devices intended for one well-defined purpose and maintain full control over them.