Skip to content

Device Management

Keep your Android fleet configured and secure.

Enroll Android devices, apply policy profiles, and deploy apps from the same platform that ordered and tracks them.

Request a DemoExplore the Platform

Built on

  • Android Enterprise
  • Android Management API
  • managed Google Play
  • Samsung Knox Service Plugin
  • Motorola OEMConfig
Illustrative interface · sample data

The problem

Device management usually starts where procurement ends.

When the management tool does not know what was ordered, teams re-enter serials, chase unenrolled devices, and lose track of who has what.

Without a connected platform

  • Device records are rebuilt by hand in a separate management console.
  • Configuration differs by manufacturer, so settings end up in separate tools.
  • Unenrolled devices go unnoticed until a user reports a problem.
  • A lost device means a ticket, a phone call, and a search for its serial number.

With Claddio

  • Devices are already serialized assets, linked to the order that delivered them.
  • Samsung Knox Service Plugin and Motorola OEMConfig settings sit alongside standard policies.
  • Enrollment status, the applied profile, and compliance appear on each asset record.
  • Lost or stolen status is set on the asset, and remote actions run through your managed device service.

Core capabilities

Android Enterprise, end to end.

Enterprise mobility management built on Android Enterprise and the Android Management API, connected to the orders and assets your teams already work with.

Provisioning

Enroll devices against a published profile.

Each enrollment setup is tied to an exact published profile, so a device receives the right settings and apps as soon as it enrolls.

  • Android Enterprise setup through the Android Management API
  • Enrollment tokens as a QR code during device setup or as an enrollment link
  • Single-use setups for a known asset, or multi-use setups for a controlled batch
  • Every enrollment attempt recorded with its profile, asset, and result
Illustrative interface · sample data

Policy management

Policies you can draft before you publish.

Prepare a profile, review it, then publish and assign it to the devices that need it. Saved changes stay unpublished until you deploy them.

  1. 1

    Draft

    Create a profile, choose device ownership and use, and add settings, apps, and network configuration.

    • Settings
    • Apps
    • Network
  2. 2

    Publish

    Review the changes, then publish the profile to Android Enterprise as a new version.

    • Published version
  3. 3

    Assign

    Assign the profile to assets, or link it to an enrollment setup for devices still to come.

    • Assets
    • Enrollment
  4. 4

    Archive

    Archive profiles you no longer use while keeping their history on record.

    • History

Device ownership and use

Every profile declares how its devices are owned and used, and Android Enterprise applies the matching management mode.

  • Company-owned

    Full management

    The whole device is managed for work. Suited to field devices and other company-issued hardware.

  • Employee-owned

    Work profile

    Work apps and data sit in a separate work profile, kept apart from personal apps and data.

  • Company-owned

    Work and personal use

    A company device with a work profile, for roles that allow personal use on corporate hardware.

Application deployment

Deploy apps through managed Google Play.

Approve apps in managed Google Play, then add them to profiles. Devices receive them through their assigned profile once it is published.

  • An app library of approved managed Google Play apps
  • Required or available installs, set within each profile
  • Assign selected apps to one or more profiles at once
  • See which profiles each app is assigned to
Illustrative interface · sample data

Device security and OEM controls

Standard policies and manufacturer controls in one profile.

Security policies and network configuration sit alongside manufacturer-specific settings, so Samsung and Motorola devices are configured from the same profile as the rest of the fleet.

  • Security policies applied through the profile
  • Wi-Fi, VPN, and certificate configuration linked to profiles
  • Samsung Knox Service Plugin, shown in Claddio as Samsung Knox Advanced Controls
  • Motorola OEMConfig, shown in Claddio as Motorola ThinkShield Advanced Controls
Illustrative interface · sample data

Managed mobility workflows

Device management that starts with the order.

Devices ordered through Claddio arrive as serialized assets, so enrollment, compliance, and remote actions attach to records that already exist.

  • Enrollment status and the applied profile on every asset card
  • Compliance posture and last-seen time next to serial, IMEI, and ICCID
  • Results of remote lock, lost mode, and wipe recorded on the asset by your managed device service
  • Lost and stolen status kept with the asset's full history
Illustrative interface · sample data

Outcomes

What IT teams gain.

  • Ready on arrival

    Devices enroll with the right profile, apps, and network settings.

  • Consistent configuration

    One policy model across standard and manufacturer-specific settings.

  • No duplicate records

    Device records come from fulfillment, not from re-entering serial numbers.

  • Changes you can review

    Profile changes stay unpublished until you choose to deploy them.

  • Faster response

    A lost device is flagged on its asset record, so the managed service acts on the right unit.

  • Clear posture

    Compliance, enrollment, and command reporting in one place.

Who it's for

Built for the teams that run device fleets.

IT teams use Device Management for their own devices; managed service providers use it to deliver device management to their customers.

FAQ

Questions about device management.

How enrollment, profiles, apps, and remote actions work in Claddio.

Claddio manages Android devices through Android Enterprise and the Android Management API. That includes Samsung devices configured with the Samsung Knox Service Plugin and Motorola devices configured with Motorola OEMConfig.

Devices enroll with enrollment tokens linked to a published profile, using a QR code during device setup or an enrollment link. Each enrollment is recorded with its profile, asset, and result.

Company-owned devices with full management, employee-owned devices with a work profile, and company-owned devices with work and personal use. The mode is set on each policy profile.

Yes. Claddio supports Samsung Knox Service Plugin and Motorola OEMConfig managed configuration through managed Google Play. In the product they appear as Samsung Knox Advanced Controls and Motorola ThinkShield Advanced Controls.

Apps are approved in managed Google Play and added to policy profiles as required or available installs. Devices receive them through their assigned profile once it is published.

Remote lock, reboot, clear app data, lost mode, wipe device, and wipe work profile are handled through your managed device service, and each result is recorded on the asset.

Yes. Reports cover device posture, compliance, and remote command results.

Devices ordered through Claddio are fulfilled as serialized assets linked to their orders, so enrollment status, the applied profile, and compliance appear on asset records that already exist.

Manage devices where you already track them.

See Android Enterprise enrollment, policy profiles, and managed apps working on the same asset records.

Request a DemoContact Sales