1. The symptom
The notification editor itself loads fine. You can write the title and the message. Then you get to targeting — and stop:
- Target Audience Type is empty. The dropdown/list offers no options, so the notification can’t be addressed to anyone.
- Hub Services doesn’t list the admins you expect. People who administer the tenant in UEM don’t appear where Hub Services expects them.
- Nothing about the message itself is wrong. This fails before content, before priority, before scheduling — at identity and audience resolution.
That combination matters. An empty audience on its own could be a scoping quirk. Empty audience plus missing admins points underneath Hub Services, to how it authenticates and looks people up.
2. What I ruled out first
Before touching Access, I checked the obvious UEM explanations — because if one of these is true for you, fix that instead:
- Organisation Group scoping. I was working as a Global Admin at the top-level OG. This wasn’t a child-OG admin who couldn’t see the parent, and it wasn’t a scoped role missing a permission.
- “Just give them a bigger UEM role.” Hub Services has its own admin model on the Access side. A bigger UEM role doesn’t automatically make someone a Hub Services admin — Hub Services Super Admin is a separate role in Access, and conflating the two sends you in circles.
- Browser / session weirdness. A fresh session didn’t change it. Missing data that survives a clean login is configuration, not cache.
The lesson in the ruling-out
Hub Services looks like a UEM feature because you launch it from the UEM world. It behaves like an Access feature underneath. When the symptom is “people and audiences don’t exist,” think Access first.
3. How Hub Services is actually wired
If that middle link is wrong, the ends can both look healthy in isolation: UEM works, Access works — but Access is pointing at an Organisation Group it can’t actually resolve, so Hub Services can’t pull audiences or admins through and the fields that depend on that lookup come back empty. That’s exactly the failure shape here.
4. The fix: the Group ID in Access has to match the Group ID in UEM
My first suspect was the OAuth 2.0 UEM client in Access (Settings → OAuth 2.0 Management → UEM) — worth a look, and it checked out fine. The actual culprit was one screen over, on the Integrations → UEM page: the Group ID field.
Here’s the shape of it, with a generic company name swapped in. In the UEM console, the root Organisation Group’s real Group ID is in UEM’s own format — say acme_root. In Access, the Group ID field held the OG’s friendly, display-style name instead — say Root Acme. Same organisation, two different strings — and Access matches on the string, not on what you meant. Pointed at a Group ID that doesn’t exist in UEM, Access can’t resolve the tenant’s users, groups, or admins — so Hub Services shows no audiences and no admins.
acme_root in this dummy tenant. This is the source of truth — copy it exactly, underscores, casing and all.- In the UEM console, read the real Group ID.Open the organisation group switcher and note the root OG’s Group ID exactly as written — in the generic example above,
acme_root, not the OG’s display name. - Go to the Access console — not UEM.Sign in to Workspace ONE Access with an admin account and open Integrations → UEM.
- Compare the Group ID field, character for character.If it holds a friendly name (like
Root Acme), a different OG’s ID, or anything other than the exact string from step 1, that’s your mismatch. - Replace it with the exact UEM Group ID and save.Copy the value directly, console to console — don’t retype it from memory, and don’t “tidy it up” into a readable name. Readable is what caused this.
- Give it a clean test.Sign out, sign back in, and open Hub Services fresh before you judge the result — you want the corrected value evaluated in a new session, not a cached one.
The screenshots above are re-created with dummy data for a fictional company, Acme — no real tenant values anywhere — but the field names, the page paths, and the shape of the mismatch are exactly as they were. That’s the transferable part, and the part I wish a search result had told me up front: when Hub Services can’t see anyone, compare the Group IDs before you touch anything else.
5. Check the other half: Hub Services admins
While you’re in Access, close the second loop the symptom exposed:
- Confirm the people who should administer Hub Services are actually listed as Hub Services admins — don’t assume the UEM admin list carries over.
- Confirm at least one person holds the Hub Services Super Admin role in Access. That role is separate from UEM admin roles.
- If the admin list is empty even for a known Super Admin, treat that as the same root-cause trail — identity resolution — not a second, unrelated bug.
6. Verify it worked
- Create a new Hub notification (don’t just re-open the broken draft).
- Target Audience Type now offers options — you can pick an audience type and resolve users/groups.
- Send a test notification to a small, known audience first — yourself or your team — before the real outage or announcement message.
- Confirm the test lands in Hub on a managed device before you rely on it for a fleet-wide notice.
If the audience still comes back empty after the client checks out, you’ve still made progress: you’ve eliminated the most common structural cause, and what’s left is a tenant-specific issue for support — with far better evidence than “the dropdown is empty.”
7. If you’re opening a case
Give support the shape of the failure, not just a screenshot of an empty field:
- The exact symptom: no Target Audience Type options when creating a Hub notification, and no admins listed in Hub Services.
- What you ruled out: admin level and OG (e.g. Global Admin at the top-level OG).
- The Group ID on the Access side (Integrations → UEM) versus the Group ID in the UEM console: what each one said, and the change you made to line them up.
- Whether Hub Services Super Admin is assigned in Access, and to whom (names/roles — never secrets).
That’s the packet that gets you past the first round of “check your admin role” replies — because you already did, and you can say so precisely.
Related reference: the MDM Almanac entry “Hub Services Group ID match” below is the one-line version of this post — the setting, where it lives, and what breaks without it. Start there next time; come back here when you need the full trail.