Signing In

Overview

UptimeHunt sign-in is email-first: enter your email address, and the login page works out every way you can sign in — a password, your company's single sign-on, and/or a social sign-in with Google or GitHub. This page explains what you will see and why.

The Email-First Flow

1. Enter your email address and continue.
2. UptimeHunt looks up the sign-in routes for that address:
   • a password account, if one exists;
   • organization SSO routes — organizations whose identity provider covers your email or where you already have an SSO account;
   • social sign-in buttons (Continue with Google, Continue with GitHub) — offered for personal email domains (gmail.com, outlook.com, and other public mail providers) when the platform has social sign-in configured.
3. What happens next depends on the routes:
   • Exactly one route, and your organization requires it → you are redirected straight to your organization's identity provider. No password prompt — see Why am I being redirected to SSO? below.
   • Several routes → an account chooser lists them explicitly (e.g. Personal, acme, Continue with Google); routes an organization requires are badged. Nothing redirects without your click.
   • No special routes → the regular password form.

Social sign-in buttons are derived from the email domain only — never from whether an account exists — so the login page does not reveal whether an address is registered.

Social Sign-In (Google / GitHub)

Continue with Google and Continue with GitHub sign you in with your personal Google or GitHub account:

• First sign-in creates your account. There is no separate sign-up step — a social sign-in with no existing account creates one, with its own personal workspace, exactly like a personal sign-up. No password is set; authentication is delegated to the provider.
• Identity follows the provider account, not the email. Changing your email at Google/GitHub does not create a new account.
• Your email is used for display and notifications. It counts as verified when the provider asserts it as verified (Google does for Workspace/Gmail accounts; GitHub for your verified primary email).
• After signing in with GitHub, you may also be able to join organizations mapped to your GitHub organizations — see SSO with GitHub.

Availability depends on the deployment's configuration — clients can discover the configured providers via GET /api/v1/auth/social-providers.

One Email, Separate Accounts

UptimeHunt treats email as a display attribute, not an identity key. The same address can belong to several separate accounts:

These accounts are never merged or linked — not automatically, not manually. Signing in with Google does not give you access to a password account with the same email; it signs you into (or creates) the Google-account realm. This is a deliberate security property: automatic email-based linking is the classic account-takeover vector, and refusing it removes that class of attack entirely. See Identity Realms for the full story.

The account chooser at login lists all routes for your email — each signs you into its own account — and the in-app account switcher can remember several accounts in the same browser and swap between them. GET /api/v1/auth/me reports which realm your current session belongs to: {"type": "password"}, {"type": "social", "provider": "github"}, or {"type": "sso", ...}.

Why Am I Being Redirected to SSO?

If your account belongs to an organization that enforces SSO, password sign-in is disabled for it — entering your email sends you straight to your organization's identity provider, and a password attempt is refused with "Your organization requires single sign-on." This is your organization's policy, not an error. If the redirect fails or no SSO button is offered, contact your organization administrator.

Signing In to a Specific Organization

If your organization shared a sign-in link of the form

https://app.uptimehunt.io/login?org={org-slug}

use it: the login page opens scoped to that organization and shows only its sign-in method. You can also pick Use single sign-on on the login page and enter the organization slug yourself. Details in Single Sign-On.

Related Documentation

• Registration — password sign-up, personal vs. team accounts
• Single Sign-On — organization IdPs, enforced SSO, identity realms
• SSO with GitHub — GitHub-based organization access
• API Authentication — the login, lookup, and token endpoints