Google OAuth
NocoDB can connect to Google OAuth 2.0. Users can then log in to their NocoDB accounts with their Google authentication credentials. This page gives the steps to integrate Google OAuth 2.0 with NocoDB.
Accessing Google OAuth Settings
The location of the NocoDB Google OAuth section depends on your plan:
| Version | Location |
|---|---|
| Cloud version | In the workspace sidebar, go to Settings > Single Sign-On (SSO). Then configure Google OAuth. |
| On-prem version | Go to Account Settings > Authentication > Google OAuth. |
Steps to Configure Google OAuth
- Verify your domain (Cloud plans only) :
- See Domain Verification.
- Copy the
Redirect URLfrom the NocoDB Google OAuth section. - Go to Google Cloud Console. Create a new project.
- Configure the OAuth consent screen
- Go to APIs & Services > OAuth consent screen.
- Enter the app details. Select the user access type.
- Add the authorized domains where NocoDB is hosted.
- Click Create.
- Generate OAuth credentials
- Go to APIs & Services > Credentials.
- Click Create Credentials > OAuth Client ID.
- For the application type, select Web application.
- Set up application details
- Authorized JavaScript origins: Enter your app domain (for example,
https://app.nocodb.com). - Authorized Redirect URIs: Paste the Redirect URL that you copied in step 2.
- Authorized JavaScript origins: Enter your app domain (for example,
- Create credentials and copy values
- Click Create.
- From the generated OAuth 2.0 Client ID, copy the Client ID and Client Secret.
- Add credentials to NocoDB
- Paste the Client ID and Client Secret into their fields in the NocoDB Google OAuth section.
For more common questions and troubleshooting, see our SSO FAQ.
Availability
- For users on the Business plan, the SSO configuration menu is in the workspace sidebar, at Settings > Single Sign-On (SSO). For more information, refer here.
- Domain Verification Required (Cloud Plans)\ \ Before you configure Google OAuth, verify your domain in NocoDB. This applies to both Business and Enterprise plans. Only users with email addresses from verified domains can sign in through SSO. For more information, refer to Domain Verification.
Last updated on
Latest product updates?See Changelog