App Catalog
What's NewStatusRoot3
  • 🌟Introduction to App Catalog
  • 🚀Getting Started
  • đŸ—ī¸Components
  • 🔒Security & Privacy
  • ✅Requirements
  • đŸ› ī¸Configuration & Deployment
    • Configuration Profile
      • Preference Keys - Catalog Agent
      • Preference Keys - Catalog App
      • Integrating with MDM
      • Configuration Profile Example
    • Installing App Catalog
    • Granting User Notifications
    • Managed Login Item
    • Full Disk Access (PPPC)
  • đŸ•šī¸Catalog Agent
    • Catalog Agent CLI
    • Installing apps
      • Dock items
      • Mandatory Apps
      • Force reinstalling apps
    • Updating apps
      • User deferrals
      • Delaying app updates
      • Updating individual apps
  • đŸ–Ĩī¸Catalog App
    • Application modes
    • User Mode
    • Admin Mode
    • Branding
      • App and notification icon
      • In-app branding
    • Language
    • Updating apps
  • 🔌Integration Guides
    • Microsoft Intune
    • Jamf Pro
    • Kandji
    • Root3 Support App
  • Troubleshooting
    • Logging
    • Error codes
    • Uninstalling App Catalog
  • ❓How To's
    • Get an app Bundle Identifier
    • Get an SF Symbol
    • Get TeamViewer Configuration ID
Powered by GitBook
On this page
  • Rules types
  • Example
  • User Experience without Configuration Profile
  • User Experience with Configuration Profile
  • Create Configuration Profile

Was this helpful?

  1. Configuration & Deployment

Managed Login Item

PreviousGranting User NotificationsNextFull Disk Access (PPPC)

Last updated 1 year ago

Was this helpful?

Starting with macOS Ventura (13), background items (such as LaunchDaemons) present user notifications and System Settings allows the user to easily disable background items. The Catalog Agent and Catalog App use a background item and users disabling it negatively impacts app-updates , the update schedule won't run and the Catalog App will not work at all. To make sure users cannot disable the background item, a Configuration Profile is needed to auto-approve and lock the background item. Most MDM solutions provide the payload from the Apple MDM framework.

Rules types

We recommend auto-approving based on Root3's TeamIdentifier to make sure all background items will run as expected and without any user approval required.

  • TeamIdentifier: 98LJ4XBGYK

Example

Below an example Configuration Profiles is provided where the TeamIdentifier will be auto-approved and locked in System Settings. This auto-approves all background items from the App Catalog and Root3 and is the easiest.

If you prefer a different way of auto-approving background items, refer to the payload from the Apple MDM framework and create your own tailored Configuration Profile.

User Experience without Configuration Profile

Below is an example of the user notification and System Settings when there is no Configuration Profile added:

  • Catalog or Root3 B.V. is mentioned when the App Catalog is installed

  • System Settings allows the user to disable the Catalog when is has administrative privileges

User Experience with Configuration Profile

Below is an example of the user notification and System Settings when there is a Configuration Profile in place:

  • The notification now show a generic message about background items managed by the organisation

  • System Settings shows the app but the user is unable to disable the background item

Create Configuration Profile

There are several ways to create a Configuration Profile for auto-approving a background item. Your MDM solution may support the payload to easily configure notifications in the user interface. If not, there are tools available that may help you creating a custom profile:

đŸ› ī¸
iMazing Profile Editor
ServiceManagementManagedLoginItems
ServiceManagementManagedLoginItems
2KB
Managed Login Items - Root3.mobileconfig