Tell us how we can make App Catalog better.
Let us know your feedback!
Automated Executive Reporting
As an IT Administrator or IT Director, I want App Catalog to automatically generate and email high-level summaries of patch compliance metrics directly to executives, so that I can consistently demonstrate the security posture and operational value of the platform to leadership without manual data compilation, ensuring key stakeholders stay informed on outstanding fleet risks.
Extended App Update Log Retention in Customer Portal
As a Security Engineer or Compliance Officer I want the App Catalog Customer Portal to retain and display app update logs for a longer duration than the current 90-day limit so that our organization remains compliant with strict regulatory frameworks (such as SOC 2, ISO 27001, HIPAA, or GDPR) that mandate long-term audit trail preservation, preventing compliance failures and historical tracking gaps during security reviews. Currently, the App Catalog Customer Portal enforces a 90-day retention limit on app update logs. While a 3-month window is sufficient for everyday operational troubleshooting, it creates a critical compliance gap for enterprise customers.
Completed
Initiate app updates instead of opening Catalog App from Notification Center
As an End User I want the "Update Now" button on an update notification to immediately initiate the app update(s) in the background rather than opening the Catalog App interface so that I can update my applications with a single click, eliminating unnecessary navigation steps, reducing workflow friction, and saving time. Currently, when a user receives a Notification Center alert regarding an available app update, clicking the "Update Now" button acts as a shortcut link. It launches the Catalog App and opens on the "Updates" tab. This behavior introduces unexpected friction: The user expects the update to start when they click "Update Now." Instead, they are forced to wait for a desktop GUI to launch. They must then visually locate the update again and click a second confirmation button inside the app. This multi-step process disrupts the user's focus and actively discourages prompt app patching.
Configurable graceful app termination
As an IT Administrator, I want the ability to configure whether an app update (when user interaction is required) enforces an immediate close or attempts a native, graceful termination request so that I can protect end-users from losing unsaved work in apps that lack macOS Auto Save support, while still retaining the ability to force immediate closures for critical security patches. Currently, the Catalog Agent terminates running apps ungracefully when the enforcement deadline is reached. If an app does not natively support macOS Auto Save architectures, users may lose unsaved data. This may result in data loss, user frustration, and increased helpdesk tickets.
Completed
Add app to Microsoft Intune using Catalog App in Admin Mode
As an administrator I’d like to be able to add apps to Microsoft Intune as a package as quickly as possible without having to download the package from Catalog App in Admin Mode and add every individual app using the Microsoft Intune interface. A “Add to Microsoft Intune“ button in Catalog App in Admin Mode would allow me to and other administrators to speed up the onboarding process dramatically. I expect Catalog App to ask me to sign-in with my Microsoft 365 account, save the token/session and allows me to add multiple apps without Catalog App asking me again for credentials, unless the token is expired. The button should result in: An app-record in Intune with the associated package including: App icon App description No assignments
Completed
1.0.0: New Customer Portal
We are modernizing the App Catalog Customer Portal and will be built completely from the ground up in an effort to adopt modern frameworks and a new design. This will give us the ability to build new features in the Customer Portal. The first step will be to launch the new portal with feature parity and then move on with some new items currently on the internal roadmap.
Allow App Catalog to update Microsoft Apps even if MAU is being configured
We are using Jamf with a configuration profile to prevent Microsoft AutoUpdate from being utilised with Microsoft Apps. We have the below configuration profile (com.microsoft.autoupdate2) restricting MAU to ‘Manual’ so that it doesn’t prompt or allow users to interact. IgnoreUIOpenAfterInstall AcknowledgedDataCollectionPolicy RequiredDataOnly HowToCheck Manual ChannelName Current EnableCheckForUpdatesButton This sufficed until now as we are Jamf Apps to manage the application updates with a 3 day defferal period, but we would now like to swap to App Catalog for deployment and updating as it’s a better user experience. Because we have this configuration profile - App Catalog will not take over the updating so I think having a key we can set in the nl.root3.catalog domain to ‘Always update microsoft apps’ or similar would be helpful.
Provide ProfileManifests with App Catalog .mobileconfig
As an IT-Administrator I want to use tools like ProfileCreator and iMazing to edit app catalog config. This will simplify adding applications to App Catalog. Please provide manifests for App Catalog to ProfileManifests https://github.com/ProfileManifests/ProfileManifests
In Research
New Title Release Notifications
It would be nice if there was an email notification/in cloud dashboard notification of when a new application is released by App Catalog to IT Administrators - Even if this was once a week that would allow us to set end user expectation.
Application List in a Data Format
It would be nice to have an exportable list of supported applications along with Bundle ID’s where we could reference and use in Data Analysis Queries.
Planned
Custom Configuration Profile - DisabledApps Function
We have a requirement to exclude a number of applications from App Catalog but still want our users to have the full benefit of the majority of applications from the catalog. However - By us wanting to exclude applications - It means we have to build a config profile from the bottom up using EnabledApps but we would much prefer to identify the 20 or so apps we don’t want users to install and hide them from the App Catalog. Using Enabled Apps also limits us from automatically receiving new applications and would have to be manually added to the catalog. If a DisabledApps function could be created it would be amazing!
Mandatory apps - Bundled apps like com.microsoft.Office365
As an IT administrator, I’d like to be sure all apps are installed correctly and mandatory apps are disabled for uninstalling. As this already works, I’d like to keep it that way when using com.microsoft.Office365. At this moment, com.microsoft.Office365 splits up in different kind of apps ( Word, Excel, PowerPoint, Outlook, OneNote and OneDrive), resulting in a daily install of the complete bundle every day. I can work around this by adding all listed apps as separate mandatory app, so it won’t install day by day the complete bundle, but it would be nice to have a way to not think about this.
Layered App Assignments in App Catalog
User Story: As an IT Administrator, I want to be able to assign apps in additive layers (e.g., a "base" profile and a "location-specific" profile), So that I can easily manage app availability for different user groups without duplicating the entire app list for each variation. Description & Acceptance Criteria: Currently, all available apps must be defined in a single EnabledApps array. This makes it challenging to manage environments with diverse needs, like multiple office locations. For example, I want to provide a core set of 15 apps to everyone in the company. For our Marketing team at the Amsterdam office, I want to add 3 extra marketing-specific apps. Right now, I have to create a separate profile for them with a list of all 18 apps. If I need to add a new core app, I have to remember to add it to every single profile, which is inefficient and prone to error. A great first step would be: Introduce a second array, let's call it EnabledApps2. The App Catalog should merge the contents of both EnabledApps and EnabledApps2 to create the final list of available apps for the user. This would allow me to push a base configuration with the first array and a supplemental configuration with the second, drastically simplifying management.
Ability to stay on a major version (avoid paid upgrades / feature loss)
I’d like to have the ability to stay on a major version of specific software, to avoid paid upgrades, but still get the latest updates of that specific version.
Catalog update feedback
As an end user, I’d like to click “Update” in the Catalog app and see an update progress indicator for each application. This would be really useful for large updates where the installer appears to hang indefinitely causing the user to believe there’s a problem.
Filter in logs
As an IT administrator, I want a simple way to filter and control application updates when a high vulnerability is discovered. This should include the option to select a specific app and version, as well as a toggle to quickly check the latest update status on each device. The expected outcome is that I can easily identify vulnerable applications, control update deployment, and ensure that devices are secured in line with policy, reducing risk exposure and improving patch management efficiency.
In Research
Docker component updates
As an IT administrator, I would like App Catalog to auto-update Docker component updates. This is needed to ensure Docker on managed Macs is fully patched.
Add our own applications to App Catalog
As an IT administrator, I want to upload and distribute our own macOS applications (.pkg or.dmg) to the App Catalog, with support for pre- and post-install scripts, so we can deploy internally developed apps and software sourced from paywalled vendors.
In Research
Administrate our admin-users as self service and IDP integration
As an IT administrator, I want to replace the current Support-based access request process with enterprise identity integrations (OIDC for SSO and SCIM 2.0 for provisioning), so that users can access the App Catalog with Single Sign-On (SSO) and their accounts (and optionally groups) are provisioned and deprovisioned automatically. Requirements Current state: Access to the App Catalog must be requested via Support. Goal: Remove this manual step and enable self-service via IdP assignment. OIDC (OpenID Connect) integration for authentication (SSO). Support redirect-based login via the IdP. Map user attributes (e.g., name, email, roles) from IdP claims. SCIM 2.0 support for provisioning. Automatic user creation, updates, and deactivation driven by the IdP. Optional: group provisioning and membership synchronization.
SIEM integration
As an IT Engineer we would like to export logs from App Catalog to an Elastic SIEM solution for centralised collection of logs. This would streamline the collection of logs. Currently, a registered user must login to view logs - they cannot be exported.