Web Content Filter
The Web Content Filter configuration integrates the content filter of a third-party app on macOS devices (filter type Plugin), for example a filter app with a Network Extension. The filtering itself is performed by this app.
macOS policies do not offer a Filter Type selection: the filter type is fixed to Plugin. The built-in filter (Built In) with Enable Auto-Filter, Blocked URLs, Permitted URLs and Allowed Bookmarks is only available in iOS policies, see Web Content Filter on iOS →. A web filter built into macOS with deny and allow lists is provided by the macOS configuration Parental Controls in the Web content filter section.
Prerequisites
- The device is supervised (badge Supervised) and enrolled via device enrollment; the configuration is not available for user enrollments.
- The provider’s filter app is installed on the device.
Configuration
Under Devices → Policies, the Web Content Filter configuration is added to a macOS policy via Add. A policy can contain several of these configurations; they are distinguished by their User Defined Name.
| Field | Description |
|---|---|
| User Defined Name | Required. Name of the filter; shown in the Name column of the policy’s configuration list |
| Plugin Bundle ID | Required. Bundle ID of the app that contains the filter provider |
| Service Address | Optional. Address of the filter service, e.g. host name or URL |
| Username | Optional. User name for signing in to the filter service |
| Password | Optional. Password for signing in to the filter service; only allowed together with a Username |
| Payload Certificate | Optional. Certificate (PKCS#1 or PKCS#12) from certificate management for signing in to the filter service; selected via Select |
| Traffic Filter Type | Socket (default) filters network traffic at socket level, WebKit filters traffic from WebKit browsers; exactly one option is active; Apple does not support WebKit filtering (FilterBrowsers) on macOS |
A stored password is not displayed in the form; the Password field then shows *****. As long as the field remains unchanged when editing, the stored password is kept. A new entry replaces it; if the field is saved empty after an entry, the stored password is removed (see Passwords and keys in configurations →). Relution automatically adds the selected Payload Certificate to the profile. A configuration with a selected Payload Certificate is not included when a policy is exported.
Example: integrating a provider’s filter app
A provider’s filter app is installed on a school’s Macs. The provider specifies the bundle ID of its app and the address of its filter service; it does not provide for signing in with a user name or certificate.
- User Defined Name:
School filter - Plugin Bundle ID:
com.example.contentfilter - Service Address:
filter.example.com - Username and Password: empty
- Payload Certificate: none selected
- Traffic Filter Type: Socket
Relution sends the devices a profile that integrates the content filter of the app com.example.contentfilter with socket-based filtering.
Enforce Safari history retention
The Enforce Safari history retention toggle applies to macOS 26 and later and is enabled by default. When enabled, the Safari history cannot be cleared on the device and Private Browsing is disabled. When disabled, the history can still be cleared.