Custom Branding

You can customize the Jamf Connect login window and menu bar app for your organization. Custom branding creates a consistent and familiar user experience for users in your organization.

You can customize the following:

  • Images and icons

  • Messages

  • Menu bar item names

  • In-app user help resources

Keep the following in mind when customizing Jamf Connect:

  • The login window and menu bar app are configured with similar but independent settings in different Jamf Connect preference domains.

  • Custom images and icons can be deployed to computers using a policy or via the Enrollment Packages payload in a PreStage Enrollment with Jamf Pro10.19 or later. Re-packaging Jamf Connect is not recommended. For more information about deploying packages with Jamf Pro, see Policy Management and Computer PreStage Enrollments in the Jamf Pro Administrator's Guide.


Using the Alternate Branding in the Menu Bar App

You can configure the menu bar app to use an alternate icon rather than the default Jamf logo and company name. This setting is suited for users who want to easily remove the Jamf branding from the menu bar app without having to package custom image files for deployment.

The alternate app icon replaces the current Jamf Connect menu bar icon and Sign In window image with the following:

To use the new icon, set the Use Unbranded App Icon (AlternateBranding) setting to true in the Appearance dictionary of your Jamf Connect menu bar app configuration profile.

<key>Appearance</key>
<dict>
    <key>AlternateBranding</key>
    <true/>
</dict>

After you switch to the alternate icon, make sure to notify end users in your organization about the menu bar icon change.

Packaging Files and Images with Composer

If you intend to use custom files or images in your Jamf Connect deployment, you can use Composer to package them. Create a package source by creating a folder on your computer where you want your custom files to be installed during Jamf Connect deployment, and then use drag-and-drop to create the new package source and build the package in Composer.

Requirements
  1. Open Finder.
  2. Press Command-Shift-G to prompt a Finder search window.
  3. Enter the file path that you want to use to store your Jamf Connect files and images during deployment, and then click Go.
    Note:

    Storing images and icons at /usr/local is recommended.

  4. Create a new folder in your chosen location.

    If creating the folder at /usr/local or another privileged space, you may be prompted to authenticate as an administrator to create the folder.

  5. Name the folder jamfconnect or something similar.
  6. Add your custom files and images to the folder.
  7. Open and authenticate to Composer, and then drag your created file from the Finder to Composer's sidebar.
    A new package source appears.
  8. Navigate to your Jamf Connect folder in Composer and configure the following ownership settings:
    1. Choose root (0) from the Owner pop-up menu.
    2. Choose wheel (0) from the Group pop-up menu.
    3. Click the Action button to the right of the X-column, and select Apply Owner and Group to jamfconnect and All Enclosed Items in the pop-up menu.
  9. For each file type in your folder, apply the following permissions:

    File Type

    Permissions

    Parent Folder

    Images

    Login window scripts

    Menu bar app scripts
  10. In the toolbar, click Build as PKG .
  11. Select a location to save the package and click Save.

Your PKG with Jamf Connect files and images can now be deployed using a policy or via the Enrollment Packages payload in a PreStage Enrollment with Jamf Pro 10.19.0 or later.

Note:

Packages must be signed using a certificate that is trusted by the computer at the time of enrollment. Signing the package with a certificate generated from either the Jamf Pro built-in CA or from an Apple Developer Program account is recommended.