Users is where you decide who is in Leanmote, whose activity belongs to whom, and what each person can see. It's a hub with five sections: Users, Teams, Roles & salary, Access levels and Bots.
The four tabs under Users
Tab | Who's in it |
Active | People who have a Leanmote account in this organization. |
Requests | People who asked to join. Approve to set their access level and add them, or reject. |
Discovered | Accounts your connected tools have seen recently that belong to nobody in Leanmote yet. |
Archived | People who used to be here. They can't sign in, and their past work still counts. |
Adding people
Two ways in, and they solve different problems.
Add user creates the account from an email address. The person gets a mail saying they've been added, with a link to sign in.
Discovered → Add as user creates the account and attaches every tool account Leanmote already found for them. That's the one to use when the person is already working — they show up in the list precisely because their work is arriving.
How that list is built matters: Leanmote reads the people who appear in the work itself — task owners and commenters, commit and pull request authors, meeting organizers. Somebody with an account but no recent activity won't appear there, so a new hire who hasn't touched anything yet has to be added with Add user.
Why mapping is the thing that matters
A person is a Leanmote user plus every tool account that is them — a GitHub handle, a Jira account, a Slack member. Leanmote maps automatically whenever it can, usually by matching email.
Until someone is mapped, they appear in no metric. Their commits, pull requests and tasks are all collected; they just belong to nobody, so they contribute to no per-person and no per-team number. This is the single most common reason a team's dashboard understates its work.
Open a person to see their mapping panel:
Suggested matches — high-confidence candidates for them. Tick the boxes to map several at once.
Accounts not mapped yet — the pool of everything found in your tools that belongs to nobody. Filter by tool or search by name, email or handle.
Use the Suggestions shortcut on the list to show only the people with candidates waiting on a decision.
Archiving, not deleting
Archiving is how someone leaves. They can't sign in any more, and their past work still counts — the history stays attributed to them, so periods when they were active still read correctly.
That's the behaviour you want when someone leaves the company: deleting the history would silently change last quarter's numbers.
Access levels
Five levels, and they add up — a person can hold more than one. Manager is what older docs call Admin, and Team Leader comes from the Teams page rather than from here. See Roles and access levels.
Some capabilities are granted person by person rather than by level. Those show a Manage access panel listing who has them, where you grant or revoke individually.
Roles & salary
The roles in your organization — "Backend Engineer — Senior" and the like — each with a default salary, assigned per person. This is what turns hours into cost in Project Financials, so a missing role means a person whose work shows up in delivery metrics but not in the money ones.
Bots
Automation accounts from your tools — CI, dependency updaters, coding agents. Leanmote already treats them as users with the Bot access level; this section is where you set a per-team override for each bot. The drawer lists every team in the organization — not the ones the bot belongs to, because bots no longer have team membership — and you mark the teams whose views should count that bot's activity.
Common issues
The same person twice — usually a tool-side rename. Map the extra accounts onto the canonical person rather than keeping two users.
One person, several identifiers 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 one person can need mapping more than once before their history is whole.
A team's numbers look low — check for unmapped accounts before suspecting the metric.
Related articles
Teams management
Roles and access levels
Mapping discovered people
SSO and SCIM