Company administration (Tandem portal)

The Tandem portal is where a company's administrator manages its GitM licence — separate from the day-to-day CAD work in the GitM add-in and the browser companion. It runs alongside GitMCloud at the same site, behind its own sign-in.

This section is for company administrators (people who onboard a company to GitM and manage its projects, members, and plan) and for Tandem operators (internal staff who provision companies). Designers and reviewers do not use the portal — they sign in with GitHub as before. See Sign in and connect.

Two sign-in doors

GitMCloud has two front doors, and they are for different people:

Door	Who	How they sign in
Sign in with GitHub	Designers, engineers, reviewers — anyone who works in the projects	Their own GitHub account (Sign in and connect)
Company admin sign in	The company's administrator	A Tandem portal login (email + password), reached from the outlined Company admin sign in link on the landing screen

Tandem operators use a third, unadvertised door at …/#/ops; it shares the same login security but is not linked from any customer-facing screen.

The GitHub-member and portal sessions are independent and coexist — signing into one never signs you out of the other, and an admin who also works in projects can hold both at once. Jump between them any time: Company admin portal ↗ (in the member app's project-switcher menu or Settings → Account) opens the portal; Open a project ↗ (in the portal avatar menu) opens the member app. Both open a new tab and are navigation only — never a logout.

The concepts

The portal is organised around a few terms that appear throughout this section:

• Customer — a company that licenses GitM. Everything below belongs to one Customer.
• Connection — a GitHub account (an organisation or a personal account) that the Customer has linked by installing the Tandem GitHub App on it. Connections are how the portal reads the company's repositories; there is no personal access token to manage.
• Project — a repository that has been initialised for GitM (it carries a .gitm/ folder). The portal discovers projects automatically under each Connection. Projects are created in the GitM desktop add-in, never in the portal.
• Member — a distinct person with access to one or more of the Customer's projects (a GitHub collaborator or someone with a pending invitation).
• Seat — one Member. A person who works on three of the company's projects still counts as a single seat.
• Plan and limits — a Customer has a maximum number of projects and a maximum number of seats. Either can be unlimited (shown as ∞). See Manage the team and seats.

Who does what

Role	Where	What they do
Tandem operator	…/#/ops	Create Customers, set plans and limits, invite the first company admin, suspend or reactivate a Customer.
Company admin	Company admin sign in	Connect GitHub, watch projects and seats against the plan, set company-wide policy, manage their own login. The pages below.

Pages in this section

You want to…	Page
Sign in, set your password, turn on two-factor	Sign in and your account
Link a GitHub account and see the company's projects	Connect GitHub
Track members and seats against the plan; set policy	Manage the team and seats

The portal never changes CAD data. It reads the company's repositories through the Tandem GitHub App and manages licence state (Customers, admins, plans) in Tandem's own store — it does not write to the .gitm/ files that GitM and GitMCloud share.