Automated Management: Devices automatically join or leave groups as they meet or fail to meet the defined criteria.

Simplified Administration: Quickly deploy policies, software, and compliance rules to specific groups.

Flexible and Scalable: Easily manage devices at any scale by creating customized conditions.

Outdated macOS Devices:

Devices Missing Antivirus:

Corporate-owned Windows Devices:

Editing Groups: Click on an existing group, update your criteria, and save changes.

Deleting Groups: Select a group and click Delete. Devices are unaffected; only the grouping is removed.

Target devices based on hardware, OS version, or custom signals

Build dynamic groups for compliance, testing, or staged rollouts

Use extension attributes for organization-specific logic

Ensure users get access to required systems immediately

Reduce manual onboarding steps

Maintain consistency across teams

Users have the correct access levels based on their device group

Permissions stay aligned as devices move between groups

Reduced risk of over-permissioned accounts

Standardize device naming conventions across your organization

Improve visibility and organization in the dashboard

Quickly identify device ownership, role, or department

During Group Creation: In the Select Commands step (Step 5), use the Run on device join column to toggle which commands should trigger automatically.

For Existing Groups: Navigate to Device Group Details > Commands tab. You can update the Run on device join settings for any assigned command.

Execution Frequency: Commands are triggered once per device per group. If a device leaves and later rejoins the same group, the "Run Once" logic will re-evaluate based on the group's current configuration.

Sequential Execution: If multiple commands are selected, they will execute in the order they appear in the configuration array.

Edge Case Handling:

Visibility and Audit: Admins can monitor execution status through the Device Status/History view. The system surfaces success, partial failure, and error states consistent with standard command history patterns.

Initial Provisioning: Automatically run a script to clear local caches or set specific environment variables as soon as a device is enrolled and categorized.

Security Hardening: Trigger a security scan or install a specific monitoring agent the moment a device enters a high-security group.

Software Deployment: Ensure that department-specific tools are installed immediately when a device is assigned to a functional group (e.g., Engineering or Sales).

Policies are applied consistently

Access is controlled dynamically

Compliance is enforced continuously

Can a device be part of multiple Smart Device Groups?
Yes. Devices join every Smart Group whose criteria they meet.

How frequently are Smart Groups updated?
Swif updates Smart Group memberships dynamically as device conditions change (e.g., after a check-in).

What happens if a Smart Group is deleted?
Deleting a Smart Group only removes the group itself. Devices remain unaffected and continue to be managed individually or by other existing groups.

How Policy, Software, and Command Assignments Are Retried
If a policy, software, or command assignment to a device fails, Swif will automatically retry the assignment every 10 minutes, up to 3 times. If the assignment is still unsuccessful after 3 retries, it will not be retried further. This ensures that temporary issues are handled automatically, while preventing excessive system load.