Docs / Enrollment / Mobile / Assignment Groups

Assignment Groups

Assignment Groups are reusable device targeting collections that simplify profile and app deployment. Instead of defining targeting rules on each profile or app package, you create groups once and reuse them across multiple deployments.

Overview

Assignment Groups provide a centralised way to manage device targeting. They are particularly useful for:

  • Maintaining consistent targeting across profiles and apps
  • Implementing staged deployments (DEV → UAT → PROD)
  • Reducing configuration duplication
  • Simplifying device organisation

Environments

Each assignment group is tagged with an environment type that indicates its purpose:

DEV (Development)

For development and initial testing. Typically contains a small number of test devices used by developers.

STG (Staging)

For pre-production testing in an environment that mirrors production.

UAT (User Acceptance Testing)

For testing by end users or stakeholders before production deployment.

SIT (System Integration Testing)

For testing integrations between systems and services.

PROD (Production)

For production devices used by end users. Deploy here only after testing in other environments.

Creating an Assignment Group

  1. Navigate to Mobile Devices > Assignment Groups
  2. Click Create Group
  3. Enter a name and description
  4. Select the environment type (DEV, STG, UAT, SIT, or PROD)
  5. Select the OS type (Android, iOS, or All)
  6. Configure targeting rules
  7. Click Create

Targeting Rules

Assignment groups use the same targeting options as profiles and apps:

All Devices

Include all devices matching the OS type. Use with caution, especially in PROD groups.

OS Versions

Target devices running specific operating system versions.

  • Android versions (e.g., 11, 12, 13, 14)
  • iOS versions (e.g., 15, 16, 17)

Management Modes

Target devices based on their management mode:

  • Android - Device Owner, Work Profile
  • iOS - Supervised, Unsupervised

Manufacturers

Target specific device manufacturers (e.g., Samsung, Google, Apple).

Models

Target specific device models (e.g., Pixel 8, Galaxy S24, iPhone 15).

Specific Devices

Select individual devices by their device ID. Useful for pilot groups or executive devices.

Exclude Devices

Exclude specific devices from the group even if they match other criteria. Useful for excluding known problem devices or devices with special requirements.

Using Assignment Groups

In Profiles

When creating or editing a profile:

  1. Scroll to the targeting section
  2. Select Use Assignment Groups
  3. Choose one or more groups from the list
  4. The profile will target all devices in the selected groups

In App Packages

When configuring an app package:

  1. Navigate to the targeting section
  2. Select assignment groups to target
  3. Configure deployment order if using multiple environments

Staged Deployments

Assignment Groups enable staged deployment workflows:

Example Workflow

  1. Create groups for each environment (DEV, UAT, PROD)
  2. When deploying a new profile or app, select DEV group first
  3. Test thoroughly on DEV devices
  4. Add UAT group and deploy (click Promote or add group)
  5. After UAT approval, add PROD group
  6. Monitor deployment status at each stage

Promote Function

Some deployment wizards include a Promote button that advances deployment to the next environment in sequence.

Device Count

Each assignment group shows how many devices currently match its targeting rules. This count is updated automatically when:

  • New devices are enrolled
  • Device properties change (OS update, etc.)
  • Targeting rules are modified
  • Devices are removed

Combined Device Count

When selecting multiple assignment groups for a deployment, you can view the combined device count. This accounts for devices that may appear in multiple groups, ensuring you know exactly how many devices will be targeted.

Editing Assignment Groups

  1. Open the assignment group details
  2. Click Edit
  3. Modify the name, description, environment, or targeting rules
  4. Click Save

Previewing Changes

When editing a group, you can preview how the changes will affect device membership:

  • Devices Added - Devices that will newly match the rules
  • Devices Removed - Devices that will no longer match
  • No Change - Devices that remain in the group

Deleting Assignment Groups

  1. Open the assignment group details
  2. Click Delete
  3. Confirm the deletion

Dashboard Statistics

The Assignment Groups dashboard shows:

  • Total Groups - Number of configured groups
  • DEV - Development groups
  • UAT - User acceptance testing groups
  • SIT - System integration testing groups
  • PROD - Production groups

Best Practices

Naming Conventions

Use clear, descriptive names that indicate the group's purpose and environment:

  • "DEV - Android Test Devices"
  • "UAT - iOS Pilot Users"
  • "PROD - All Corporate iPhones"
  • "PROD - Samsung Galaxy Devices"

Environment Strategy

  • Always test in non-production environments first
  • Keep DEV groups small (5-10 devices)
  • Use UAT for broader testing before production
  • Document which profiles/apps target which groups

Maintenance

  • Review group membership periodically
  • Update targeting rules when device fleet changes
  • Archive unused groups instead of deleting if needed for audit
  • Document changes to production groups

Troubleshooting

Device Count Seems Wrong

  • Check if devices are enrolled and active
  • Verify targeting rules match device properties
  • Check for exclude rules that may be filtering devices
  • Ensure OS type matches the devices you expect

Deployment Not Reaching Expected Devices

  • Verify the correct groups are selected
  • Check device count in the group
  • Review individual device properties
  • Ensure devices are online and syncing