Prerequisites
- A Google Workspace account with admin access
- A verified domain in Google Workspace
- Admin access to LowerPlane Settings
Setup Steps
Create OAuth credentials in Google Cloud
- Go to the Google Cloud Console.
- Create or select a project.
- Navigate to APIs & Services > Credentials.
- Click Create Credentials > OAuth 2.0 Client ID.
- Select Web application as the application type.
- Set the Name to
LowerPlane SSO.
Configure Redirect URI
In the OAuth client settings, add the Authorized redirect URI. Copy the Redirect URI shown on LowerPlane’s SSO settings page and paste it here.It will look like:
https://api.lowerplane.com/api/v1/auth/sso/callback/oidcCopy Client ID and Client Secret
After creating the OAuth client, Google will display:
- Client ID (e.g.,
123456789.apps.googleusercontent.com) - Client Secret
Enter credentials in LowerPlane
In LowerPlane, go to Settings > SSO and select Google as your provider:
- Client ID: Paste the Client ID from Google
- Client Secret: Paste the Client Secret from Google
Configure domain restriction
Restrict sign-in to your organization’s email domain (e.g.,
@yourcompany.com). This prevents personal Google accounts from accessing your organization.How It Works
- A user visits your LowerPlane login page and clicks Login with SSO.
- They enter their email address and LowerPlane detects the Google SSO configuration.
- The user is redirected to Google’s sign-in page.
- After successful authentication, Google sends an authorization code to LowerPlane’s redirect URI.
- LowerPlane exchanges the code for tokens, fetches the user profile, and logs the user in.
Configuration Details
| Setting | Value |
|---|---|
| Protocol | OAuth 2.0 / OpenID Connect |
| Authorization URL | https://accounts.google.com/o/oauth2/v2/auth |
| Token URL | https://oauth2.googleapis.com/token |
| Userinfo URL | https://www.googleapis.com/oauth2/v3/userinfo |
| Scopes | openid, profile, email |
| Redirect URI | Shown on LowerPlane SSO settings page |
Troubleshooting
Users see 'Access Denied' during Google sign-in
Users see 'Access Denied' during Google sign-in
Ensure the user’s Google Workspace account is part of your organization and has not been suspended. Personal Gmail accounts cannot be used for SSO.
Redirect URI mismatch error
Redirect URI mismatch error
The Redirect URI in Google Cloud Console must match exactly what is shown on LowerPlane’s SSO settings page. Copy it directly — even trailing slashes or HTTP vs HTTPS differences will cause failures.
SSO works but user gets 'Account not found'
SSO works but user gets 'Account not found'
The user must be added to your LowerPlane organization before they can sign in via SSO. Add them from Settings > Users.
Domain restriction not working
Domain restriction not working
Verify the domain is entered exactly as it appears in your Google Workspace admin console (e.g.,
yourcompany.com not www.yourcompany.com).