How to control who shows up in Collaborate (v2.5.1)
The Recents tab is always populated with the most recent people you interacted with on the device. We record the people who directly called you, or you called. If you log in to another teams account - the Recents tab will be refreshed for that account, restoring the last locally known recent contacts.
Collaborate Contacts come from Microsoft 365 / Azure AD. The config file (config.json, pushed via RealWear Cloud / MDM) gives you two levers: which directory the Contacts tab pulls from, and which groups to hide.
Lever 1 — contactsSource (what actually fills the Contacts tab)
This picks which Microsoft Graph query runs. Real behavior of each:
| Value | What the contacts tab shows | Under the hood |
| "organization" (default) | Only internal employees of your Azure tenant. Guest/external accounts excluded. | Graph /users, filtered to your org domain. Requires User.ReadBasic.All |
| "orgAndExternals" | Everyone in organization plus guest accounts invited into your tenant (partners, contractors). | Graph /users, no filter. Requires User.ReadBasic.All |
| "peopleWithChats" | A per-person relevance list, three sources merged: (1) always — org people that user actually interacts with (People relevance ranking, org users only); (2) if permitted — external/guest org users; (3) if permitted — people from the user's Teams chats (incl. external). Not the whole company. | Base: Graph /me/people (org users only). Appended in parallel + de-duped: /users (external only) and Teams chat members. People.Read = min (unlocks tab); User.ReadBasic.All → adds external org users; Chat.ReadWrite → adds chat contacts |
Lever 2 — blacklistedGroupIds (the only per-group control in v2.5.1)
{ "blacklistedGroupIds": ["<azure-ad-group-id>", "..."] }
"blacklistedGroupIds" hides those Azure AD groups and their members from Contacts / My Teams. Max ~180 IDs. Warning: "blacklistedGroupIds" can also only fully hide groups with up to ~4995 members (a Microsoft Graph query paging cap); any blacklisted group larger than that will have some of its members still appear in Contacts and team member lists.
Not directly in v2.5.1. There's no allowlist yet (we plan to ship in the next releases). Your options today:
1. Blacklist everything else — list all other groups in blacklistedGroupIds, leaving X visible. Works if you have ≤180 other groups.
2. Isolate in Azure AD — put X's people in a dedicated group/OU and blacklist the rest.
3. Narrow the source — contactsSource: "organization" to at least strip out all guests/externals.