This guide is intended for organizations that need to install Comet at large scale. If you’re looking for the individual Comet installer, you’ll find it here.
This guide covers deploying the Comet browser across your organization using Mobile Device Management (MDM) solutions on macOS systems.
To install Comet for Enterprise using MDM you will need:
An MDM solution (Jamf Pro, Intune, Kandji, Mosyle, Workspace ONE, etc.)
Access to your organization's Comet settings at perplexity.ai/account/org/comet
Your organization token (available from the Comet Setup page)
Mac policies are deployed using Configuration Profiles (.mobileconfig files) through your MDM solution. These profiles use the ai.perplexity.comet payload type to configure Comet settings.
First, you’ll need to download the Comet installer and obtain your organization token from: perplexity.ai/account/org/comet.
The Comet for Enterprise installer is currently available as a .dmg macOS disk image.
For mass deployment using tools like Jamf Pro:
Upload the .dmg file to your MDM solution
Prepare a script that mounts the DMG, copies the Comet app to /Applications, and unmounts the DMG
This script can be part of your post-install tasks or included in the package
Use post-install scripts to:
Handle app copy
Set permissions
Make Comet the default browser if required
Configure first run settings (via plist manipulation if needed)
Jamf Pro allows you to deploy and manage custom application settings in two different ways.
Using just the plist content (without the full mobileconfig wrapper), where Jamf handles wrapping it into a proper configuration profile.
Using custom JSON schema to provide a UI-based approach to managing policies (unique to Jamf)
Go to Computers → Configuration Profiles → New
Enter a display name (e.g., "Comet Policies")
Select Application & Custom Settings → External Applications
Select Upload
Preference Domain: ai.perplexity.comet
Paste the plist content from the examples below
Go to the Scope tab
Add target computers or groups
Click Save
Before configuring browser policies, you must first enroll devices into your organization. This associates each Comet installation with your enterprise account for centralized management.
Get your organization token from perplexity.ai/account/org/comet and deploy the following plist:
\
\
\
\
\CloudManagementEnrollmentToken\
\YOUR-ORG-TOKEN-HERE\
\
\
Once devices are enrolled, you can deploy additional configuration profiles to enforce browser policies. See examples below.
\
\
\
\
\ExtensionInstallBlocklist\
\
\
\nkbihfbeogaeaoehlefnkodbefgpgknn\
\
\
\
\
\
\
\
\URLBlocklist\
\
\chatgpt.com\
\\*.competitor.com\
\
\
\
Combine multiple policies in a single plist:
\
\
\
\
\ExtensionInstallBlocklist\
\
\nkbihfbeogaeaoehlefnkodbefgpgknn\
\
\URLBlocklist\
\
\chatgpt.com\
\
\
\
Go to Computers → Configuration Profiles → New
Enter a display name (e.g., "Comet Policies")
Select Application & Custom Settings → External Applications
Select Add
Preference Domain: ai.perplexity.comet
Select Add Schema
Paste JSON Schema to populate configurable properties from the examples below
Go to the Scope tab
Add target computers or groups
Click Save
Example: Homepage and startup settings
\{
"title": "Perplexity Comet – Homepage and Startup",
"description": "Control homepage, startup behavior, and New Tab configuration.",
"properties": \{
"HomepageLocation": \{
"title": "Homepage Location",
"description": "URL of the homepage that is loaded when the Home button is pressed.",
"type": "string",
"property\_order": 10
},
"HomepageIsNewTabPage": \{
"title": "Homepage Is New Tab Page",
"description": "If true, the homepage is the New Tab page instead of a custom URL.",
"type": "boolean",
"property\_order": 20
},
"ShowHomeButton": \{
"title": "Show Home Button",
"description": "Shows or hides the Home button in the toolbar.",
"type": "boolean",
"property\_order": 30
},
"RestoreOnStartup": \{
"title": "Restore On Startup",
"description": "Configures what pages are shown at startup.",
"type": "integer",
"enum": \[0, 1, 4],
"options": \{
"enum\_titles": \[
"0 – Open the New Tab page",
"1 – Restore the last session",
"4 – Open a list of URLs"
]
},
"property\_order": 40
},
"RestoreOnStartupURLs": \{
"title": "Restore On Startup URLs",
"description": "List of URLs to open on startup when RestoreOnStartup is set to 4.",
"type": "array",
"items": \{
"type": "string"
},
"property\_order": 50
},
"NewTabPageLocation": \{
"title": "New Tab Page Location",
"description": "Custom URL to use for the New Tab page instead of the default.",
"type": "string",
"property\_order": 60
},
"ManagedBookmarks": \{
"title": "Managed Bookmarks",
"description": "JSON-like structure defining a set of mandatory bookmarks managed by policy.",
"type": "array",
"items": \{
"type": "string"
},
"property\_order": 70
},
"BookmarkBarEnabled": \{
"title": "Bookmark Bar Enabled",
"description": "Shows or hides the bookmarks bar by default.",
"type": "boolean",
"property\_order": 80
},
"DefaultBrowserSettingEnabled": \{
"title": "Default Browser Setting Enabled",
"description": "Controls whether the browser can be set as the system default.",
"type": "boolean",
"property\_order": 90
},
"BlockExternalExtensions": \{
"title": "Block External Extensions",
"description": "Blocks extensions installed outside the browser when set to true.",
"type": "boolean",
"property\_order": 100
}
},
"required": \[]
}
Example: Force install extensions - e.g., 1Password and Okta Verify
\{
"title": "Perplexity Comet – 1Password and Okta Extensions",
"description": "Toggle force-install for 1Password and Okta extensions in Comet.",
"properties": \{
"ForceInstall\_1Password": \{
"title": "Force install 1Password",
"description": "If enabled, Comet force-installs the 1Password browser extension.",
"type": "boolean",
"default": false,
"property\_order": 10
},
"ForceInstall\_OktaPlugin": \{
"title": "Force install Okta browser plugin",
"description": "If enabled, Comet force-installs the Okta browser plugin defined below.",
"type": "boolean",
"default": false,
"property\_order": 20
},
"OktaPluginExtensionId": \{
"title": "Okta browser plugin extension ID",
"description": "Chrome Web Store extension ID for your Okta browser plugin (for example, from the Web Store URL).",
"type": "string",
"default": "",
"property\_order": 30
},
"ExtensionInstallForcelist": \{
"title": "Additional force-installed extensions (advanced)",
"description": "Optional: extra entries in the form extension\_id;\<[https://clients2.google.com/service/update2/crx](https://clients2.google.com/service/update2/crx)>. Rows here are in addition to 1Password/Okta switches above.",
"type": "array",
"items": \{
"type": "string",
"title": "Extension ID and update URL",
"default": "extension\_id;\<[https://clients2.google.com/service/update2/crx](https://clients2.google.com/service/update2/crx)>"
},
"property\_order": 40
},
"\_info": \{
"title": "Info",
"description": "Jamf will write a prefs key named ExtensionInstallForcelist. Enable the switches above to add 1Password and/or Okta automatically; use the array only for extra extensions.",
"type": "string",
"options": \{
"inputAttributes": \{
"readonly": true
}
},
"property\_order": 50
}
},
"required": \[]
}
For MDM solutions that require a complete .mobileconfig file, such as Kandji, Mosyle, Fleet, SimpleMDM, etc., use the full configuration profile format below.
Copy the example template and customize for your needs
Generate unique UUIDs for PayloadUUID fields (use uuidgen in Terminal)
Save as a .mobileconfig file
Upload to your MDM as a custom configuration profile
Assign to target devices or groups
Before configuring browser policies, you must first enroll devices into your organization. This associates each Comet installation with your enterprise account for centralized management.
Deploy a configuration profile containing your CloudManagementEnrollmentToken. Get your organization token from perplexity.ai/account/org/comet.
\
\
\
\
\PayloadContent\
\
\
\PayloadType\
\ai.perplexity.comet\
\PayloadIdentifier\
\ai.perplexity.comet\
\PayloadUUID\
\A1B2C3D4-E5F6-7890-ABCD-EF1234567890\
\PayloadVersion\
\1\
\CloudManagementEnrollmentToken\
\YOUR-ORG-TOKEN-HERE\
\
\
\PayloadDisplayName\
\Comet - Organization Enrollment\
\PayloadIdentifier\
\ai.perplexity.comet.org-enrollment\
\PayloadType\
\Configuration\
\PayloadUUID\
\B2C3D4E5-F6A7-8901-BCDE-F23456789012\
\PayloadVersion\
\1\
\
\
Once devices are enrolled, you can deploy additional configuration profiles to enforce browser policies. See examples below.
\
\
\
\
\PayloadContent\
\
\
\PayloadDisplayName\
\Comet Extension Blocklist Policy\
\PayloadIdentifier\
\ai.perplexity.comet\
\PayloadType\
\ai.perplexity.comet\
\PayloadUUID\
\12345678-1234-1234-1234-123456789012\
\PayloadVersion\
\1\
\ExtensionInstallBlocklist\
\
\
\nkbihfbeogaeaoehlefnkodbefgpgknn\
\
\
\
\PayloadDisplayName\
\Comet - Extension Blocklist\
\PayloadIdentifier\
\ai.perplexity.comet.extension.blocklist\
\PayloadType\
\Configuration\
\PayloadUUID\
\87654321-4321-4321-4321-210987654321\
\PayloadVersion\
\1\
\
\
\
\
\
\
\PayloadContent\
\
\
\PayloadDisplayName\
\Comet URL Blocklist Policy\
\PayloadIdentifier\
\ai.perplexity.comet\
\PayloadType\
\ai.perplexity.comet\
\PayloadUUID\
\12345678-1234-1234-1234-123456789012\
\PayloadVersion\
\1\
\URLBlocklist\
\
\chatgpt.com\
\\*.competitor.com\
\
\
\
\PayloadDisplayName\
\Comet - URL Blocklist\
\PayloadIdentifier\
\ai.perplexity.comet.url.blocklist\
\PayloadType\
\Configuration\
\PayloadUUID\
\87654321-4321-4321-4321-210987654321\
\PayloadVersion\
\1\
\
\