The promise of centralized device management is that one person can oversee hundreds or thousands of devices from a single dashboard. The reality in many deployments is that the device list is a flat, ungrouped inventory, and every action that needs to apply to more than one device requires either selecting them individually or pushing to the entire fleet indiscriminately.
Neither approach scales. Individual selection is manual work that grows linearly with fleet size. Pushing to all devices means a content update meant for signage displays goes to POS terminals too, and a configuration change for one location affects every location in the fleet.
Device groups solve this. When configured thoughtfully, groups let you push an app update to every Android kiosk in the Midwest region with a single action, change the content profile for digital signage displays at your airport locations without touching any other device type, and monitor all devices at a specific facility as a unit without scrolling through an undifferentiated list of hundreds.
This is how Moki’s group structure transforms fleet management from a device-by-device operation into a genuinely scalable system.
What Device Groups Actually Do
In Moki’s MDM platform, device groups are collections of enrolled devices that share a configuration profile, receive updates together, and can be monitored as a unit. Any action that can be performed on a single device can be performed on an entire group simultaneously:
- Push an app installation or update to all devices in the group
- Apply or update a configuration profile across the group
- Push content to all signage or kiosk devices in the group
- Schedule a reboot for all devices in the group during a maintenance window
- View the aggregate health status of all devices in the group from a single dashboard view
- Set alert thresholds that apply consistently to every device in the group
Groups can be nested or overlapping depending on how the platform is configured, allowing a device to belong to a location group and a device-type group simultaneously, making it eligible to receive both location-specific content updates and device-type-specific configuration changes.
The Three-Layer Group Structure
The most effective group structures for multi-location device fleets use three organizing layers that correspond to the three most common targeting needs in day-to-day fleet management.
The first layer is location. Every device belongs to a location group that corresponds to the physical site where it is deployed. This makes location-level operations straightforward: pushing a content update to all devices at the Denver store, monitoring the status of all devices at the Phoenix facility, or rebooting all devices at a specific location during an off-hours maintenance window are all single-group operations when location groups are in place.
The second layer is device type or use case. Every device belongs to a group that reflects what it does: kiosk, POS terminal, digital signage, employee handheld, check-in terminal. This layer enables functional targeting: an app update for the self-ordering kiosk application goes only to kiosk devices, not to signage displays or handheld devices, even if all three types are deployed at the same location.
The third layer is platform. In any fleet that includes both iOS and Android devices, or that includes BrightSign players alongside tablet-based devices, platform groups ensure that configuration pushes and firmware updates target the correct hardware. An iOS configuration profile pushed to Android devices does nothing at best and causes errors at worst. Platform groups prevent that entirely.
With these three layers in place, any targeting scenario in routine fleet management is addressable as a group operation. A specific location, a specific device type, a specific platform, or any combination of the three can be targeted precisely without manual device selection.
Building Groups Before Enrollment
The most important timing advice in group configuration is to build the group structure before the first device is enrolled, not after. Devices that are enrolled into the correct groups from the start have the right configuration applied immediately and appear in the correct monitoring views from day one. Devices that are enrolled without group assignment and organized later require retroactive work that creates a window of misconfigured or unmonitored devices.
The pre-enrollment group building process should:
- Define the complete list of location groups based on all current and near-term planned deployment locations
- Define device type groups for every category of device in the fleet
- Define platform groups if the fleet is or will be mixed-platform
- Map out which configuration profile applies to each group combination
- Document the group structure in the device deployment playbook so new devices and new locations are enrolled consistently
This setup investment is front-loaded but pays back continuously. Every device enrolled after the structure is in place drops into the right groups automatically and receives the correct configuration without additional action.
Using Groups for Content Management
Content management is one of the highest-frequency use cases for device groups, particularly for digital signage and kiosk deployments where content changes on a regular cadence.
A typical content management workflow using groups looks like this: the marketing team prepares updated content for a seasonal promotion. The IT or operations team uploads the content to Moki and selects the signage display group for the relevant region. The push is initiated and the content deploys to every device in that group simultaneously. Devices in other groups, including POS terminals, kiosks running a different app, or signage displays in locations that are not part of the promotion, are unaffected.
Without groups, the same update requires either selecting each signage device individually or pushing to all devices and filtering out the noise. With groups, it is three clicks.
For restaurant operators running menu boards, this means a price change or limited-time offer goes live at every location simultaneously. For retail chains managing promotional displays, a campaign launch is a single group operation rather than a location-by-location coordination effort.
Using Groups for Configuration Management
Configuration management is where the depth of a well-structured group system becomes most apparent. Different device types need different configurations. A kiosk needs strict single-app lockdown. A POS terminal needs payment app configuration and network restrictions. A signage display needs content management and scheduled reboot settings. An employee handheld needs app access controls and a less restrictive lockdown profile than a customer-facing device.
When each device type has its own group with its own configuration profile, updating the configuration for one device type is a single profile edit that propagates to every device in that group automatically. Adding a new app restriction to all kiosks across all locations is one profile change, not 200 individual device updates.
This is also where platform groups prove their value. If a security policy update needs to be applied to all Android devices, the Android platform group receives it. iOS devices are unaffected. If an iOS supervised mode configuration needs to be updated, it targets the iOS group without touching Android or BrightSign devices.
Using Groups for Monitoring
Beyond pushing configurations and content, groups make monitoring operationally useful. A fleet of 300 devices viewed as a flat list is difficult to interpret. The same fleet organized into location groups, device type groups, and platform groups becomes a structured view where the health of any segment of the fleet is visible at a glance.
When an alert fires for a device at a specific location, the location group view immediately shows whether the problem is isolated to that device or whether multiple devices at the same location are affected. Multiple simultaneous alerts from the same location group often indicate a network issue at that site rather than individual device failures. A single device alert in a location where all others are healthy points to a device-level problem.
This contextual awareness, enabled by group structure, changes the speed and accuracy of incident response. The team knows immediately whether they are dealing with one device or a site-wide outage, and can escalate or respond accordingly.
Maintaining the Group Structure Over Time
A group structure that is well-designed at launch but not maintained becomes cluttered and less useful over time. Groups accumulate devices that have been decommissioned, locations that have closed, and device types that are no longer deployed. Regular group hygiene is part of the periodic MDM audit process and should be reviewed at least quarterly.
Maintenance tasks include removing decommissioned devices from groups, adding new device types to the correct groups at enrollment, archiving groups for locations that have closed, and reviewing whether group structures still reflect the current operational reality of the fleet.
Moki’s support team is available to help with group structure design during initial setup and with reorganization as the fleet evolves.
Schedule a Moki demo to see device group management in action across a multi-location fleet, or start a free trial to begin building your group structure today. Moki’s eBooks cover fleet organization best practices in more depth for teams planning large-scale deployments.