# FileWave 13.1 TCC Payload Separation (Historical)

<p class="callout info">This page records a FileWave 13.1 profile migration. For current configuration steps, use [Create TCC Privacy Policy Control Payloads](https://kb.filewave.com/books/profiles-apple/page/create-tcc-privacy-policy-control-payloads).</p>

## Change introduced in FileWave 13.1

FileWave 13.0 stored macOS TCC privacy settings inside a single **Security &amp; Privacy** payload. FileWave 13.1 separated TCC settings from the General, FileVault, and Firewall settings so administrators could deploy privacy controls independently and use more than one TCC payload.

## Legacy Profile Editor layout

The screenshots below show the two payloads in the FileWave 13.1 Profile Editor.

### Security &amp; Privacy - iOS and macOS (10.7+)

This legacy payload contained General and FileVault settings for macOS plus Firewall and Privacy settings.

[![image.png](https://kb.filewave.com/uploads/images/gallery/2023-07/scaled-1680-/rQxKc9CNimap9GXo-image.png)](https://kb.filewave.com/uploads/images/gallery/2023-07/rQxKc9CNimap9GXo-image.png)

### Security &amp; Privacy - macOS (10.14+)

This separate legacy payload contained the macOS TCC Privacy and Consent Control settings.

[![image.png](https://kb.filewave.com/uploads/images/gallery/2023-07/scaled-1680-/O6uvgizyCc0WxUXM-image.png)](https://kb.filewave.com/uploads/images/gallery/2023-07/O6uvgizyCc0WxUXM-image.png)

## Historical 13.0 to 13.1 migration

When a FileWave 13.0.x profile containing TCC settings was migrated to 13.1, the converted profile displayed both Security &amp; Privacy payloads. The recommended migration was to create one profile for General, FileVault, and Firewall settings and a separate profile for TCC privacy settings.

Separating TCC settings also allowed administrators to deploy multiple privacy payloads independently.