Signing In
TracePath accounts live at app.tracepath.dev (opens in a new tab). There are three ways to get into one, and they all resolve to the same account:
| Method | Where |
|---|---|
| Email and password | app.tracepath.dev/login (opens in a new tab) |
| Continue with Google | Same page, above the password form |
| Continue with GitHub | Same page, above the password form |
New accounts start at app.tracepath.dev/register (opens in a new tab). Signing up with Google or GitHub creates the account in the same step, then walks you through naming your organization and first project.
Verifying your email
A password signup sends a verification link to the address you registered with. It expires an hour after it is sent, and signing in is gated on it, so verify before you go looking for your project token. Request a fresh one from the login page if it expired or never arrived; check spam before writing in.
Google and GitHub signups skip this step. The provider has already verified the address, which is the whole point of the match described below.
Two-factor authentication
The sign-in flow challenges any account that has TOTP enabled: after the password it asks for a six-digit code from your authenticator app, or one of your recovery codes. Five wrong codes lock further attempts for fifteen minutes.
There is no screen in the dashboard to turn it on yet, so in practice no self-serve account has it today. If two-factor is a requirement before you can adopt TracePath, write to [email protected] rather than assuming the toggle is somewhere you have not looked.
Linking a social login to an existing account
The match is made on the verified email address the provider returns:
- If you have signed in with that provider before, you are logged straight back into the same account.
- If the email already belongs to a password account, the social identity is linked to it. Either method works from then on, and no second account is created.
- Otherwise a new account is created.
So you can register with a password today and click Continue with Google tomorrow, as long as both carry the same address.
GitHub only hands over a verified primary email. If your GitHub account has no verified email, the sign-in is rejected and you are sent back to the login page with an error. Verify the address in GitHub's own email settings and try again, or sign in with a password.
Joining an organization
An organization invitation is tied to the email address it was sent to. Accept the invite from the link in that email; if you have no account yet, accepting one creates it. Signing in with Google or GitHub on an address that has a pending invitation puts you in the same place.
Members are added, removed, and re-roled from Settings → Team Members by an organization owner or admin. See Organization Overview for what the roles control.
Per-tenant SSO is not offered today
TracePath does not currently support connecting your own identity provider — no per-organization OIDC or SAML, no SCIM provisioning, no domain capture, and no enforced-SSO policy. The Google and GitHub buttons above are the only federated options, and they authenticate against Google and GitHub directly rather than against your IdP.
If enforced SSO is a requirement for your organization, write to [email protected] and say which provider you use. It is on the roadmap; it is not shipping, and nothing in the product will pretend otherwise.
Losing access
- Forgot your password: use the reset link on the login page. The email is sent to the address on the account.
- Lost access to the Google or GitHub account: if the TracePath account also has a password, use that. If it does not, reset the password from the login page — the reset goes to the same email address the provider gave us.
- Removed from your last organization: your account still exists. Sign in and create a new organization, or ask to be re-invited.
Related
- CLI Authentication: how
tracepathsigns in without your password. - MCP Server: OAuth with PKCE for MCP clients.
- Organization Overview: roles, members, and what each one can do.