Where discovered people live
People are not a tab in Discoveries. If you came here looking for one, it moved: external people your connected tools report are on the Users page, in the Discovered tab — "people your connected tools report who are not in Leanmote yet".
Discoveries handles repositories, boards, statuses and channels. People are handled next to the rest of your users, because mapping a person is a decision about your user list, not about what Leanmote should measure.
Why mapping matters
Leanmote's own explainer on that page says it in three steps:
You connect a tool in Integrations. Its activity starts flowing into Leanmote.
You map each person to their tool accounts. That's what tells Leanmote whose activity it is.
Until someone is mapped, they appear in no metric.
That third line is the one that costs teams a quarter of their data without anyone noticing. An unmapped engineer's commits, pull requests and tasks are all collected — they just don't belong to anybody, so they contribute to no per-person and no per-team number.
Leanmote maps automatically whenever it can, usually by matching email addresses. What lands in Discovered is what it couldn't decide on its own.
Two things you can do there
Add as user creates a Leanmote user and attaches every tool account already found for that person in one step. It's the right action when the person works here and simply isn't in Leanmote yet.
Map attaches found accounts to a person who already exists. Use it when the user is there and only some of their accounts are linked.
One caveat about how the list is built: Leanmote reads the people who appear in the work itself — task owners and commenters, commit and pull request authors, meeting organizers. Somebody with a tool account but no recent activity won't appear, so a new hire who hasn't touched anything yet has to be added by hand.
Mapping someone
Open a user to see their mapping panel. It has two lists:
Suggested matches — high-confidence candidates for this person. Tick the checkboxes to map several at once.
Accounts not mapped yet — the pool of accounts found in your tools that belong to nobody in Leanmote yet. Filter by tool or search by name, email or handle, then map the ones that are this person.
Map applies it. One person often needs several mappings, because the same engineer is a GitHub handle, a Jira account and a Slack member, and Leanmote has to know all three accounts are the same person.
Finding the ones that need you
Filter the user list by mapping state, or use the Suggestions shortcut to show only the people with candidate accounts waiting on your decision. That's the shortest path from "we have unmapped activity" to a decision.
When someone keeps coming back
One person can hold more than one identifier in the same tool — commits under a username and others under a personal email, for example. Each identifier is its own account in the pool, so a person can need mapping more than once before their history is whole.
Related articles
Users management
Discoveries — overview
Why a metric looks off