> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getprimo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Device naming

> Use AI to automatically generate and enforce consistent device names across your macOS, Windows, and Linux fleet based on employee and device attributes.

## Platform compatibility

| macOS | Windows | Linux | iOS / iPadOS | Android |
| ----- | ------- | ----- | ------------ | ------- |
| ✅     | ✅       | ✅     |              |         |

## How to set it up

<Steps>
  <Step title="Write a naming prompt">
    Write a prompt that defines the automated naming structure for your devices. Be specific for optimal results — for example, describe the format using device type, serial number, or employee name.

    Include instructions for edge cases such as devices without a serial number or unassigned devices. Allowed characters: letters, numbers, and hyphens.

    <Info>
      Keep names under 15 characters if you need compatibility with older network systems that enforce NetBIOS name length limits — this is especially relevant for Windows devices.
    </Info>
  </Step>

  <Step title="Preview the generated names">
    Use the preview to verify the output before deploying.
  </Step>

  <Step title="Select targeting">
    Choose which devices to apply the control to: all devices, specific device groups, or a custom target.
  </Step>
</Steps>

## Modify or remove the control

Disable the control from the profile settings. Disabling stops enforcement but does not remove existing configurations from devices.

## How it works

When a device is enrolled or its assigned employee changes, Primo evaluates the naming prompt and pushes the generated hostname to the device via MDM. The update happens silently in the background — no user interaction or restart is required.

Names are re-evaluated automatically whenever the underlying attributes change, keeping your inventory current.