A profile is an additional preference level for the application that takes priority over the usual preferences. The operating system manages all profiles and preferences. It allows applications to use only the preferences that the operating system gets from profiles, preferences, or both.
To use profile preferences in the application, profiles must have the correct application domain specified:
You can use following settings to create custom profiles:
You can use any MDM solution, such as ProfileCreator or iMazing Profile Creator. Here’s an example of the profile that you can use for MindManager:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
PayloadUUID is the globally unique identifier for the payload. The actual content is unimportant, but must be globally unique. In macOS, use uuidgen to generate a Universally Unique Identifier (UUID). You can run this command in the Terminal app and replace <UUID1> with the generated ID. To replace <UUID2>, generate another ID. For more information about profiles, consult Apple support for Configuring Multiple Devices Using Profiles Platform.
You can also create system profiles to hide or display System Preferences. This can be useful if you want to hide Profiles from the user. To create system profiles, you can also use Apple Configurator, in addition to a range of third-party tools.
This feature was deprecated by Apple and only works on macOS 13.0 and earlier.
Profiles have the same logic as Admin control panel, but for offline builds of MindManager for Mac. Profiles do not affect the MindManager for Mac builds that are online; the MindManager Admin Panel takes priority.