This is the Owner's path, condensed. Leanmote's guided setup is seven steps; here is what each one is for and roughly what it costs you. It saves as you go, so stopping halfway loses nothing.
It ends with your metrics in Context, the section where views live. If that word is new, What is Context? explains it in two minutes — but you can also just follow the steps and read it afterwards.
1. Name the organization (2 minutes)
The name everyone sees — sidebar, invitations, shared views. Use what your team says out loud. You also set the organization's language, which becomes the default for everyone you add.
Can't be skipped.
2. Pick your tools (2 minutes)
Which tools your team already uses. You're building the shortlist for the next step, not connecting yet. Pick generously.
3. Connect tools (10 minutes)
The step with no way past: with nothing connected there is nothing to show you. Sign in at each provider and authorize read access. Prefer organization-level installs over personal accounts, which die when the person leaves.
Remember that credentials are per person — connecting on behalf of the organization doesn't make your own work visible.
4. Review the people it found (5 minutes)
Leanmote lists the people seen in your tools, deduplicated, with service accounts and off-domain emails already unticked. Correct what it got wrong.
Adding someone and emailing them are separate: everyone ticked is added either way, and the invitation section only decides who gets a mail.
5. Build teams (5 minutes)
Each team needs a leader. Choose Dynamic — membership follows whoever worked on the chosen boards and repositories in the last 90 days, rechecked nightly — or Manual, where you name the people.
6. Match accounts (3 minutes, or later)
Say who each unmatched account is, or that it isn't a person. Whatever you leave waits in Discoveries. It's the step most worth finishing: an unmatched account's work counts toward nobody.
7. Your dashboards (3 minutes)
The step is still called Your dashboards in the step rail, but what it builds are views in Context: one per team, filtered to that team and pinned in the sidebar under Context. The chips on each team are the sections that view will show — one you don't tick is left out, and nothing is written until you press Continue.
Targets are proposed here too; change them, or untick them and set them once you've seen real numbers.
Then: a weekly rhythm
The setup ends with data arriving. What makes it useful is looking at it on a cadence — one view, once a week, with one question. The Performance Delivery tabs of your team's view on Monday are the most common starting point.
Related articles
Welcome to Leanmote
What is Context?
Connect your first integrations
Run your first sync and open your first view