Staff and sign-in matching
An AI tool reports activity under whatever it knows about a person: an email address, a vendor account, a Microsoft account. StackJack must decide which record belongs to which person on your staff…
Written By Christopher Scaminaci
Last updated 13 days ago
An AI tool reports activity under whatever it knows about a person: an email address, a vendor account, a Microsoft account. StackJack must decide which record belongs to which person on your staff list. This page explains how it matches, what "unmatched" means and how to link two records into one person. It also covers the Staff page and name reveals.
At a glance
- What it does: builds your staff list, matches sign-ins to people and handles name reveals.
- Plan: every plan.
- Who: Administrator, Reviewer or Reveal approver. Linking and splitting need an Administrator.
- Where: AI Governance → People → Staff and People → Staff sign-ins.
- Needs: at least one source. An EU or UK organization also needs its staff notice.
Apps and automations
A sign-in that is really a bot or a service is not a person. People → Apps and automations lists the applications and automations you attribute machine use to, and offers to turn a detected sign-in into one. See Apps and automations.
Your staff list
StackJack builds your staff list from the people in your organization's StackJack account. If you use Entra directory sync, it also uses your Microsoft directory.
How StackJack matches a record to a person
StackJack links a record to a person on your staff list only when an identifier matches exactly:
- the same Microsoft directory account,
- the same StackJack sign-in, or
- the same email address as a person in your directory or in the member list of a vendor you connected as an administrator (Anthropic or OpenAI).
It never links two records because a name or a company domain looks alike. It never links two people who are both on your staff list.
What "unmatched" means
A record is unmatched when someone used an AI tool in the last 30 days under an identity that is not on your staff list. Nothing is judged until your first staff import has finished. StackJack says why each one is unmatched:
- Possible personal account (a consumer mail address)
- An address outside your company domains
- A vendor account with no email address
- A company address nobody on your roster holds
An unmatched sign-in appears under Unmatched sign-ins and raises an "Unmatched identity" alert. An administrator can link it to a person with Link to a person, or select Dismiss, for example for a known contractor.
Link two records
Two linked records count as one person: in your staff count, on the person's own page, and when the person is erased. Activity that was already recorded is not rewritten. It stays as it was received, under the record it arrived on.
A link can be undone at any time. In Linked records, select Split. An undone link puts the sign-ins back where they were. Exclusions and legal holds that a link copied stay with the person after a split.
Company or personal account
Where the tool says which organization an account belongs to, StackJack uses that. Otherwise an email address on one of your company domains is a company account, an address on a well-known consumer mail service is a personal account, and anything else is shown as not known. You can edit your company domains and your company's vendor organizations on the Settings tab of the Staff sign-ins page. The Vendor organizations tab is where you confirm a connection that now reaches a different vendor organization. Activity recorded before you changed them is not reclassified.
Staff groups
A group is a list of people. You make your own on the Groups tab of the Staff sign-ins page. Groups from your Entra directory appear beside them and follow it. You cannot edit those here. Groups are used to address alerts.
The Staff page
People → Staff lists the people whose AI use is recorded. Each row shows the Person, Findings (30 days) and First seen. A person appears as they use AI.
From the Staff page an administrator can open the Erase this person dialog. See Erasing a person. Nothing on this page scores or ranks a person.
Names and reveals
Your name policy decides what you see. Under the pseudonymous policy, a reviewer sees a label such as "Staff member 4F2A". To see the name:
- A Reviewer asks to see the name. They give a reason and a case reference.
- A Reveal approver decides. They cannot approve their own request.
- The decision and the reveal are recorded in the audit trail.
The Staff page shows requests waiting for a decision, and the requests you asked for. Under the policy that shows names to administrators, people whose role has Sees names see names. Everyone else sees a pseudonym. See Privacy, notices and retention settings.
Troubleshooting
More help is in Troubleshooting and FAQ, by symptom.
Next
Was this helpful?
More in See what is happening
The Overview, card by cardThe Activity explorerSpend and budgetsStill need help? Ask the team