The moment a tool is connected, history starts arriving. The rest of the guided setup is about turning that raw activity into numbers that belong to somebody.
What the first sync does
Leanmote reads backwards as far as the tool and your choices allow, then keeps up incrementally. A small workspace is done in minutes; a large one with deep history can take up to a day. Your views fill in as data lands, so the first hours look emptier than the first day.
After that first pass, refresh runs on a schedule — roughly every twelve hours — not continuously. Worth knowing before the first time you check: a "last synced" timestamp several hours old is normal, and something you changed in your tool this morning may not show up until tonight.
The people it found
The next step opens with a count: the people seen in your tools, deduplicated — someone who appears in three tools counts once.
Leanmote has already made two decisions for you, and it says so rather than hiding them:
Service accounts are unticked. Bots, CI, dependency updaters. Tick one back if it got it wrong.
People whose email is not on one of your domains are unticked. Contractors and clients, usually. Tick back the ones who work with you.
One distinction here saves confusion later: adding someone and emailing them are two different things. Everyone you leave ticked is added either way; the invitation section only decides who gets a mail asking them to sign in.
Teams
Every team needs a leader — that's who gets to see the team's numbers and share views. Pick one and the team is created.
There are two kinds, and the difference matters more than it looks:
Dynamic — members are whoever worked on the boards and repositories you pick, over the last 90 days. Rechecked every night, so the team keeps up with who actually works on it.
Manual — exactly the people you name, until you change them.
A dynamic team is the honest default for a codebase-shaped team. A manual one is right when membership is a fact about your org chart rather than about the work.
Match accounts to people
Whatever couldn't be matched automatically comes here: say who each account is, or that it isn't a person. Anything you leave waits for you in Discoveries — nothing is lost, but nothing counts either. An unmatched account's work belongs to nobody, so it lands in no per-person and no per-team number.
Your dashboards
The last step is called Your dashboards, and what it creates are views in Context: one per team, with that team's filter already applied, pinned in the sidebar under Context. Each chip on a team is a section that view will show; one you don't tick is left out. Nothing is written until you press Continue.
It also proposes targets, which you can change or untick — "not yet, I'll set these once I've seen the numbers" is a supported answer and often the right one.
A view is yours until you share it. By default only the team's leader opens it.
Reading your first numbers
Open your team's view under Context. A view shows its metrics as tabs, and the four that answer the delivery questions are Workflow Performance for flow, Software Delivery Performance for DORA, Team Collaboration Network for how review work is distributed, and Team Overview for the per-person table.
All the tabs of a view share one set of filters, set once in the top bar — so the date range you pick for flow is the same one DORA answers with. You can add more tabs at any time with Add a tab.
Give it a full period before drawing conclusions. A first week of data is a first week of data, not a trend.
If something reads as a dash or a zero
That's usually configuration rather than a bug, and there are three usual causes: the date range predates what was backfilled, an account isn't matched to a person, or a workflow status is classified wrong. See Why a metric looks off.
Related articles
What is Context?
Connect your first integrations
Why a metric looks off
Missing data after connect
Teams management