Connecting a tool is the step the guided setup won't let you past, and the reason is simple: with nothing connected there is no data, so every screen after it would be empty.
The one thing to understand first
Credentials are per person, not per organization. Your organization having GitHub connected does not mean your work is being read — that happens when you connect your own account. It's why every access level, down to Collaborator, is asked to connect tools, and why a manager who connected Jira still sees their own activity missing until they connect it themselves.
Where it lives after setup
From the left-hand sidebar, expand Administration and click Integrations. The page you land on is titled Productivity Tools and lists every integration Leanmote supports, grouped by category. During the guided setup you get the same list, filtered to the tools you picked in the previous step.
Connecting a source-control tool
Find the tool — GitHub, GitLab, Bitbucket or Azure DevOps — and click Connect.
Sign in at the provider and authorize Leanmote on the scopes it asks for. Leanmote only reads your data, but on some providers the grant itself is broader than read: GitHub's
reposcope covers read and write because there is no read-only equivalent for private repositories, and Jira and Azure DevOps include a work-item write permission. Each integration's article lists exactly what it asks for.Choose the scope where the provider offers it. GitHub and Linear let you pick which repositories or projects; other providers grant at the account or site level and there is no narrower choice to make.
Prefer an organization-level install over a personal one where the provider offers it — a GitHub App on the org, an Atlassian site-admin install. A connection made under someone's personal account dies when that person leaves.
Connecting a planning tool
Same shape: Connect, sign in, approve the scopes, and pick the projects or boards that matter. Boards are worth a moment of care — activating a board brings its workflow statuses with it, and those statuses are what become cycle time and waiting time.
What happens the moment you connect
Leanmote starts reading immediately and, with automatic activation on, starts measuring what it finds rather than waiting for you to approve each repository. Your job becomes switching off what shouldn't be measured, in Discoveries.
It also starts finding people: the accounts that appear in the work itself. Those land in the setup's next step, and anything you don't resolve waits in Discoveries.
If a connection fails or goes quiet
Disconnected means the stored credentials stopped working — a token expired, or the person who connected it left. Reconnect from the same page; no data is lost.
Nothing arriving after a connection that looks healthy is usually scope: the repository or project you expected isn't in the selection.
Related articles
Sign in and create your organization
Run your first sync and open a dashboard
Integration shows disconnected
Sync isn't completing