DDM Component Layout

DDM declarations are JSON files that define device configurations. Understanding the structure helps you troubleshoot deployments or customize declarations.

Component Types

The project generates DDM declarations that work together:

Type	Purpose
Activation	Enables a configuration on the device
Configuration	Defines what settings to apply

Common Structure

All DDM declarations share these keys:

Key	Description
`Identifier`	Unique identifier for this declaration
`Type`	The Apple declaration type
`Payload`	The declaration-specific settings

Activation Declaration

Activations enable configurations on the device.

{
  "Identifier": "org.mscp.baseline_name.activation.service",
  "Type": "com.apple.activation.simple",
  "Payload": {
    "StandardConfigurations": ["org.mscp.baseline_name.config.service"]
  }
}

Key	Description
`StandardConfigurations`	Array of configuration identifiers to activate

Configuration Declaration

Configurations define the settings to apply. For service configurations:

{
  "Identifier": "org.mscp.baseline_name.config.service",
  "Type": "com.apple.configuration.services.configuration-files",
  "Payload": {
    "ServiceType": "com.apple.service",
    "DataAssetReference": "org.mscp.baseline_name.asset.service"
  }
}

Key	Description
`ServiceType`	The Apple service being configured
`DataAssetReference`	Identifier of the asset containing the config files

Next Steps

How to Generate DDM Components - Create DDM files from your baseline
What is DDM? - Learn more about declarative management