Connected accounts (Google + Facebook)

You can sign in to the Snippbot marketplace using Google or Facebook — no password required. You can also connect a social account to an existing password-based account, then sign in either way.

This guide covers:

• Signing up for the first time with Google or Facebook
• Connecting a social account to an existing password account
• Disconnecting a social account
• What happens if your provider account is compromised
• Email-collision errors

Sign up with Google or Facebook

1. Go to the marketplace sign-up page.

2. Click Continue with Google or Continue with Facebook at the top of the form.

3. Approve the permission on the provider’s consent screen. We only request your email address.

4. You’ll land on the Finish your account page. Confirm your username (we suggest one based on your email; you can edit it to anything 3–40 lowercase letters, digits, or hyphens that isn’t already taken), confirm your display name, and check the Terms of Service checkbox.

5. Click Create my account. Done — you’re signed in.

Note

Facebook signups also get a verification email. Because Facebook doesn’t reliably tell us whether your email is verified, we send our own verification message after sign-up. You’ll need to click the link in that email before you can buy a license or access paid Packages. Until then, the rest of the marketplace works normally.

Sign in with Google or Facebook (returning users)

1. Go to the login page.

2. Click Continue with Google or Continue with Facebook.

3. If you’ve signed in before with that provider, you’ll usually skip the consent screen and land directly on your dashboard. The provider remembers your prior consent.

If your account has multi-factor authentication enabled, we’ll prompt for a 6-digit code from your authenticator app before signing you in. This is the same flow as password sign-in — Google and Facebook aren’t trusted to bypass MFA.

Connect a social account to an existing password account

If you signed up with a password and want to add Google or Facebook as a secondary sign-in option:

1. Sign in to your account with your password.

2. Go to Settings → Connected accounts.

3. Click Connect Google or Connect Facebook.

4. Approve the consent screen.

5. You’ll be redirected back to Settings with the provider listed as connected.

You can connect both Google and Facebook to the same account if you want.

Email-collision errors

When you click Continue with Google with a Google account whose email matches an existing Snippbot account that was created with a password (and which has not yet connected Google):

We refuse the sign-in and show this banner on the login page:

An account with [email protected] already exists. Sign in with your password, then connect Google from Settings.

This is intentional. Trusting Google to vouch for your email and merging the accounts would let anyone who creates a Google account at your email address take over your Snippbot account. Instead, you prove ownership of the email by signing in with your password, then explicitly connecting Google from Settings.

If you’ve forgotten your password, follow the forgot-password flow first, then connect Google from Settings.

Disconnect a social account

1. Go to Settings → Connected accounts.

2. Click Disconnect next to the provider you want to remove.

3. A modal asks if you’d also like to sign out of all your devices. Useful if your provider account was compromised — checking this revokes every active session, not just the link.

4. Click Disconnect.

When you disconnect, we make a best-effort call to the provider’s API to revoke our access token (Google: https://oauth2.googleapis.com/revoke; Facebook: DELETE /me/permissions). If that call fails — for example, because Facebook has already revoked the token on their end — we still remove the link locally; the revoke side is non-critical.

Caution

You can’t disconnect your only sign-in method. If you signed up with Google and have never set a password, disconnecting Google would lock you out. The disconnect button surfaces a “Set a password first” prompt in that case — pointing at Settings → Security → Change password. After you set a password (which we treat as the same operation as a password reset for security purposes), you can disconnect Google.

The same rule applies if you have only Google connected — even multiple linked providers count as one safety net each. Always keep at least one working sign-in method.

What we get from the provider

We request only your email address and (where the provider includes them in the basic userinfo) your display name and profile picture URL. We do not request:

• Friend lists or social graph data
• Drive / Photos / Calendar / Contacts data
• Posting permissions
• Any “sensitive” or “restricted” scopes that would trigger a Google verification review

We use the email to identify your Snippbot account; we don’t sell it, share it for marketing, or send you anything other than transactional emails (license confirmations, package updates, security alerts) that are critical to your account.

For the full data flow + retention policy, see the Marketplace Privacy Policy, Section 6.1.

Troubleshooting

“Continue with Google/Facebook” button doesn’t appear. The provider may not be enabled in your environment. Hard-reload the page (Cmd/Ctrl + Shift + R) to clear any cached state. If the button still doesn’t show, contact support — it usually means the provider’s credentials are temporarily down on our end.

“App not active” from Facebook. This means we’re operating in Facebook’s development mode for your environment. Wait for the App Review approval (typically 3–14 days), or use the email/password path while we get reviewed.

“Verification timed out” on the MFA challenge. The 6-digit code window is short — about 5 minutes after we issue it. Click your browser’s back button and sign in again to get a fresh code.

Stuck in a loop where I’m signed in but the dashboard shows “Sign in required”. Open a private/incognito window and sign in there. Then come back to the main browser, clear cookies for singularitymarketplace.com, and sign in fresh. This is rare and usually means a stale singularity_session cookie collided with the new OAuth one.

If anything else goes wrong, email [email protected].