This policy deploys Web Clips to managed macOS devices, providing users with quick access to specific web resources directly from their home screen. By standardizing access to essential company portals and tools, organizations can significantly improve user productivity and ensure a secure, unified browsing experience across the fleet.
This is a device level policy that applies system-wide to the device and all of its users. You can bind this policy to individual devices or device groups. For policies that apply to a specific user's profile across devices, see Get Started: Policies and Learn More section of this article.
Prerequisites
- macOS devices must be enrolled in Apple MDM with the following enrollment type:
- Device-Enrolled Devices - These devices are owned by the corporation, and enrolled by the admin or by the user.
- User-Enrolled Devices - These are personal devices used for work where the user enrolls the device to securely access corporate data while maintaining personal privacy.
- Auto-Enrolled Devices - These devices are owned and enrolled by the corporation through Automated Device Enrollment.
For more information, see MDM Enrollment Method.
- Target devices must be running macOS 17 or later.
Considerations
- The policy configuration settings are applied automatically and do not require a system restart.
Creating the Policy
To create a WebClip policy for Mac computers, do the following:
Selecting the Policy Template
- Log in to the JumpCloud Admin portal.
If your data is stored outside of the US, check which login URL you should be using depending on your region. If your organization uses LDAP, RADIUS, or requires firewall allow list configuration, the Fully Qualified Domain Names (FQDNs) will also be region specific. See JumpCloud Data Centers for the URLs, FQDNs, and IP addresses.
- Go to Device Management > Policy Management. The Policy Management page is displayed.
- On the Policy Management page, click +Add New.
- Select Device Policy to assign the policy to devices and device groups. On the New Device Policy page:
- Select the macOS tab.
- Search and select the required policy and click Configure. The Details tab of the policy is displayed.
- On the Details tab, configure the required policy configuration settings.
- (Optional) In the Policy Name field, enter a new name for the policy or keep the default. Policy names must be unique.
- (Optional) In the Policy Notes field, enter details such as creation date of the policy, and information on testing and deployment of the policy.
Configuring the Policy
Configure the following under the Settings section:
- IsRemovable - Enable this option to allow users to delete the WebClip from their devices.
- Label - Provide a concise name for the WebClip. This text will appear directly under the icon on the user's Home screen.
- URL - Enter the web address you want the shortcut to open. Ensure the address begins with HTTP or HTTPS to guarantee a successful connection. For example, https://console.jumpcloud.com
Under the Icon Image, the following options are available:
- Icon - Upload a PNG, GIF, or JPEG to give your WebClip a custom look.
- Precomposed - Select this to prevent Apple’s SpringBoard from adding a shine or glossy sheen to the icon when it is displayed on the user’s home screen.
Applying the Policy
- (Optional) Select the Policy Groups tab. Select one or more policy groups where you want to add this policy.
- Select the Device Groups tab. Select one or more device groups where you want to apply this policy to. For device groups with multiple OS member types, the policy only applies when a user logs into a supported Windows device that is enrolled in MDM.
- Or, select the Devices tab. Select one or more devices where you want to apply this policy.
- Click Create Policy. A success message is displayed indicating the completion of policy creation.
Viewing Policy Status
- Select the Status tab.
- To see the last Result Log for a device where this policy is applied, click view.
- If any errors occur, they're listed in Exit Status. If you have an Exit Status of 0, no errors occurred when applying or enforcing this policy.