Topic
This article enables you to define a specific configuration profile that NinjaOne will apply to devices assigned to the policy. NinjaOne deploys each custom payload as a separate MDM profile to the device.
Environment
- NinjaOne mobile device management
- Apple iOS and iPadOS
Description
Custom payloads allow NinjaOne to support all Apple MDM payloads even if the UI does not reflect support. There may be a small delay in implementing new functionalities introduced by Apple, but we will expedite the appropriate solution.
To learn more about Apple configuration profiles and profile-specific payloads, refer to Apple's developer documents.
Add a custom payload in NinjaOne
- In the Custom payload section of an Apple MDM policy, click Add payload.
The Add payload configuration modal displays. - Give the payload an identifiable name. In the Content field, insert the payload properties into the colored code block.
Figure 12: Add a custom payload in a NinjaOne Apple MDM policy
- Click Update.
- Once created, you can edit or delete the payload by moving your cursor over the row and clicking the ellipsis button.
Required Keys
One or more valid dictionaries must define the payload content. You must manually enter the p-list ("property list" file format) text. You may also include optional keys; NinjaOne will deploy them as configured.
Optional keys are not validated, but the system will verify that they comply with the p-list-based structure.
Updating custom payloads
Optionally, you can add a payload identifier and UUID. If you do not include one, NinjaOne will create a generic identifier (for example, "com.NinjaOne.Custom.[GUID]").
Additional Resources