After a health-department inspector signs in, Intelligent Hub shows Salesforce-for-government, the city intranet, and a Horizon desktop icon in one catalog. Which Workspace ONE product authenticated the user and assembled that mixed catalog?
Select an answer to reveal the explanation.
Short Explanation
Think of Access as the city hall badge desk that also hands you one laminated directory of every office you may enter. After the inspector proves who they are, Hub can show Salesforce, the intranet, and a Horizon tile from that same catalog. Intelligence, DEM, and App Volumes do not mint that SSO catalog.
Full Explanation
For a health-department inspector who signs in and then sees Salesforce-for-government, the city intranet, and a Horizon desktop icon together in Intelligent Hub, Workspace ONE Access is the product that authenticated the user and assembled that mixed catalog. Access is the identity broker and SSO application catalog for SaaS, web, and virtual applications; after Access proves who the inspector is and which entitlements apply, Hub can present those tiles in one civic launcher. Think of Access as city hall’s badge desk that also hands over one laminated directory of every office the inspector may enter—SaaS portals, intranet sites, and entitled Horizon resources—without treating each tile as a separate product. Workspace ONE Intelligence fails the scenario by concept: it is the analytics and dashboard plane over UEM and related telemetry, so it reports what happened last week rather than minting or authenticating the Hub catalog. Dynamic Environment Manager fails because it personalizes the Windows user environment—drive maps, shortcuts, and ADMX-driven settings inside a desktop session—and those settings do not become Hub catalog tiles after SSO. App Volumes fails because it attaches application packages and writable volumes to Horizon desktops; packaging a layer for a VDI guest is not the same as Access listing SaaS, web, and virtual entitlements in Intelligent Hub. Exam caveat: Hub is the employee-facing shell that displays the catalog; Access is still the identity and entitlement source for the mixed launch experience, and a Horizon tile in Hub does not mean Access replaced Horizon Connection Server as the session broker. Operational check: have the inspector authenticate through Access into Intelligent Hub, confirm Salesforce, intranet, and Horizon tiles appear from Access entitlements, and verify that opening an Intelligence dashboard or attaching an App Volumes package does not by itself recreate that SSO catalog.