The city wants entitled Horizon virtual apps, and historically Citrix collections, to appear as catalog sources in Workspace ONE Access. Which component historically integrates those on-premises virtual-app collections?

When the city wants entitled Horizon virtual apps—and historically Citrix collections—to appear as catalog sources in Workspace ONE Access, the component that historically integrates those on-premises virtual-app collections is Workspace ONE Access Connector (its virtual-app collection components), which collect entitlements into Access. Access Connector is the clerk who walks into the Horizon or legacy Citrix back office and brings entitled apps back to the Hub catalog. Workspace ONE Intelligence fails by concept: Intelligence does not screenshot Horizon icons and publish them as catalog widgets; analytics is not virtual-app entitlement sync. Horizon Help Desk fails because exporting a CSV of pools for Access to email to clerks is not how entitlements are integrated—Help Desk is for session and user troubleshooting. Workspace ONE Boxer fails because Boxer is the managed email, calendar, and contacts client; attaching a Blast shortcut to civic mail is not the Access virtual-app collection path. Exam caveat: catalog appearance still requires proper Horizon (or historical Citrix) integration settings, entitlements, and user sync; Connector health matters, and listing a virtual app in Access does not remove the need for Horizon infrastructure when the user launches it. Operational check: configure or review virtual-app collections on Access Connector for Horizon entitlements, confirm those apps appear in the Access/Hub catalog for a test user, and verify Intelligence, Help Desk, and Boxer were not the integration source.