> ## 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.

# Generate settings via AI

> Use Primo's AI engine to create tailored MDM configuration profiles for Apple devices in seconds by describing the settings you need in plain language.

## Platform compatibility

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

## How to set it up

<Steps>
  <Step title="Describe the configuration you want">
    Describe the configuration you want in plain language. For example:

    * *"Disable Bluetooth on all devices"*
    * *"Set the DNS servers to 1.1.1.1 and 8.8.8.8"*
    * *"Enable automatic screen lock after 2 minutes of inactivity"*
  </Step>

  <Step title="Review the generated profile">
    Review the generated profile — Primo will show you the resulting configuration before deployment.

    <Warning>
      Always review the generated profile before deploying. AI-generated configurations may require adjustments depending on your specific environment. Test on a small device group before rolling out broadly.
    </Warning>
  </Step>

  <Step title="Adjust and save">
    Adjust any settings if needed, then save and apply the control to the relevant device group.
  </Step>
</Steps>

## How it works

The AI engine produces a standard Apple `.mobileconfig` profile based on your description. The generated profile:

* Uses native Apple MDM payloads.
* Can be reviewed and edited before deployment.
* Is deployed to devices in the same way as any other Primo control.

**Tips for better results**

* Be specific about the setting and the desired value.
* Mention the context if relevant (e.g. "for shared devices" or "for the sales team").
* If the first result is not exactly right, refine your description and regenerate.

<Info>
  If you already have an existing `.mobileconfig` file you want to deploy, use the **Custom file** control instead.
</Info>