Troubleshooting: Social Login Problems

GridGap supports social sign-in with Google, Microsoft, and LinkedIn. Most problems here come from redirect mismatches, blocked popups, provider-session confusion, or signing in with a different email address than expected.

What this usually means

If social sign-in fails, the provider may not have completed the handoff back to GridGap, the provider account may not expose the email address the app needs, or the flow may be returning to a page that expects a different account context.

Common causes

Common causes include popup or redirect blocking, signing in with the wrong Google, Microsoft, or LinkedIn account, starting from an invitation flow and then using a different email address, or retrying after the social session has expired.

What to check

First retry the sign-in using the exact provider account that should own the GridGap account or invitation. If the problem happens from a workspace invitation page, make sure the provider account uses the invited email address. If the provider flow returns you to login with an error, try a full sign-out from the provider, then start the sign-in again from GridGap rather than from a saved provider session.

If social sign-in still fails but you know the account email, try the standard email-and-password route instead. If you never set a password because the account began as social-only, use the contact form or, if you can still access another part of the app, open a support ticket.