Sign in with Google, GitHub, Discord or Microsoft
You can sign up for SunLicense and sign in to the dashboard with your Google, GitHub, Discord or Microsoft account instead of a password. Choose Continue with GitHub (or another) on the sign-in or sign-up page, or on sunlicense.com/start.
- No account yet: you get a new account and organization on the Free plan, named after your email address (rename it in onboarding). If the provider has verified your email address, you don't need to confirm it again. Microsoft accounts are the exception: you'll get the usual "confirm your email" message.
- Already have an account with the same email: Google, GitHub and Discord accounts whose email the provider has verified are connected to it automatically, and we email you that a new sign-in method was added. Otherwise (a Microsoft account, an email the provider hasn't verified, or a SunLicense account whose email you never confirmed) sign in with your password once and connect the provider under Settings → Account → Sign-in methods.
- Guest accounts: a guest account a coding agent made for you (guest accounts) can be claimed with a provider too: open the claim link and choose Continue with ….
Manage your sign-in methods
Settings → Account → Sign-in methods lists your password and every connected account, with when you last used each.
- Connect another provider: you go to the provider, approve, and come back to Settings.
- Remove one you no longer use. You can't remove your last way to sign in: set a password or connect another account first.
- Set a password (accounts made with a provider have none): we email you a link to choose one, the same as "Forgot password?".
Your sign-in methods are your account's, so they work in every organization you belong to.
The CLI
sunlicense login signs in with an email and password. If your account has no password, either set one (above) or create a personal access token under Settings → Access tokens and run:
echo "$TOKEN" | sunlicense login --with-tokenWhat the provider shares
Your account ID at the provider, its email address and whether it's verified, and your display name. We never see your password there, never post anything for you, and don't keep the provider's access token. See the privacy policy.
Not covered
Single sign-on for a whole company (SAML or your own identity provider), Apple and passkeys aren't available yet. The system admin console keeps its own password and authenticator code, and the customer portal has its own "Sign in with Discord" for your customers.