Connect GitHub¶
The portal reads your company's repositories through the Tandem GitHub App. You link each GitHub account your company uses by installing that app on it — this is called making a Connection. There is no personal access token to create or paste.
Prerequisites¶
- You are signed in to the portal as your company's admin. See Sign in and your account.
- You can install a GitHub App on the account you want to connect. For a GitHub organisation that means being an org owner (or having the org approve the install); for a personal account, being that user.
Connect an account¶
- Open the Connections tab.
- Click Connect GitHub. The portal opens GitHub's install screen for the Tandem GitHub App.
- Choose the organisation or personal account to install on, and which repositories the app may see (all repositories, or a selected set). Approve the install.
- GitHub returns you to the portal, which shows a Connected banner. The account now appears in the Connections list.
Each Connect GitHub click creates a one-time secure link, so the account you install on is bound to your company automatically. If an account is already connected to a different Customer, the portal reports a conflict instead of binding it twice.
What a Connection gives the portal¶
Once an account is connected, the portal can, using the app's install token:
- Discover projects — every repository under that account that has been initialised for
GitM (carries a
.gitm/folder) shows up on the Projects tab. - Count members and seats — it reads each project's collaborators and pending invitations to build the team and seat view.
The app token is read-only for these purposes and is scoped to the connected account. The portal never stores your repositories — it reads them live from GitHub.
Projects¶
The Projects tab lists the company's GitM projects discovered across all Connections. For each project you see its visibility, default branch, last activity, and a link to open it on GitHub. The list is read-only:
Projects are created in the GitM desktop add-in, not here. A designer or CAD admin sets a repository up for GitM (see Set up a team repository); the portal then discovers it automatically under the matching Connection.
If a connected account has no projects yet, or an account you expected is missing, check that the repository has been initialised for GitM and that the app was granted access to it during the install.
Manage or remove a Connection¶
- Use Manage next to a connected account to open its install on GitHub — for example to add or remove repositories the app can see.
- To disconnect an account entirely, uninstall the Tandem GitHub App from it on GitHub (its Settings → GitHub Apps). Its projects and members stop being counted; the portal degrades gracefully rather than erroring.
Troubleshooting¶
| Symptom | Cause | Fix |
|---|---|---|
| "Conflict" after installing | The account is already connected to another Customer | Connect a different account, or ask a Tandem operator to sort out the binding |
| Account connected but no projects | No repository under it is initialised for GitM, or the app can't see them | Initialise a project in the add-in; check the app's repository access under Manage |
| A project is missing | The app install excluded that repository | Manage the Connection and grant the app access to it |
| Members look under-counted | The app lacks permission to read invitations on some repos | Re-check the app install; pending invitations need the app's read access to a repo's administration |
Known limitations¶
- Removing a Connection is done by uninstalling the app on GitHub, not from the portal.
- The portal lists projects; opening a project's files, BOM, or history is done in GitMCloud or the GitM add-in.