Connect Your Google Account For Social Login
This guide will help you to add your Google account for Google Sign up/in. This means the jobseeker won't see Artha's name when doing social sign up/in using LinkedIn.
Before You Start - What You'll Need
Make sure you have these ready before beginning:
✅ A Google account (Gmail or Google Workspace account)
✅ Your company logo saved as an image file (optional but recommended)
✅ A business email address (can be Gmail for Business or any business email)
✅ Your website's exact URL (the web address where your job seekers log in)
Important Note: You'll be doing the setup on Google's side, but you won't need to touch any code or configure anything technical yourself. The Artha Support Team will handle all the technical backend work once you share some information with them.
⚠️ Special Note About Google: Unlike some other social login options, Google requires a verification and approval process for your application. This means there will be a waiting period (typically 1-2 weeks) before the "Sign in with Google" feature can go live.
Understanding Key Terms (Simple Glossary)
Before we begin, here are a few terms you'll see. Don't worry - you don't need to be an expert, just know what they mean:
Google Cloud Console - A special website where companies can manage their connections with Google's services. Think of it as Google's control center for businesses.
Project - A container that holds all your settings and configurations for connecting your job portal with Google. It's like a folder that organizes everything related to your Google login setup.
OAuth 2.0 - A secure way for websites to let users log in using accounts from other services (like Google). You don't need to understand how it works - just know it's the technology that makes "Sign in with Google" possible.
Client ID - A unique identification number Google gives you (like a username). It's public and safe to share.
Client Secret - A secret password Google gives you (like a password). Keep this private and secure.
API - A way for two computer systems to talk to each other. In this case, it's how your job portal communicates with Google.
Redirect URL - The web page address where users land after logging in with Google. For your job portal, this is typically your login page.
OAuth Consent Screen - The page users see when they click "Sign in with Google" - it tells them what information your job portal will access and asks for their permission.
Scope - Specific pieces of information your job portal can access from a user's Google account (like email address, name, profile picture).
Step-by-Step Instructions
Step 1: Access Google Cloud Console
What you're doing: Going to Google's special area where businesses can connect their websites with Google services.
Open your web browser and go to: https://console.cloud.google.com
Click the "Sign In" button (usually in the top right corner)
Log in using your Google account credentials (your Gmail or Google Workspace email and password)
You'll know you're in the right place when: You see a page with "Google Cloud" at the top and a dashboard showing various Google Cloud services.
Step 2: Create or Select a Project
What you're doing: Creating a new "project" which is like a dedicated workspace for your job portal's Google login setup. Everything related to your Google login will be organized under this project.
Look at the very top of the page, near the Google Cloud logo
You'll see a project dropdown (it might say "Select a project" or show an existing project name)
Click on this dropdown
In the popup window, click "New Project" (usually in the top right corner of the popup)
Fill in the project details:
Project name: Give it a clear name
Example: "JobSphere Google Login" or "YourCompanyName Portal Login"
This is just for your reference - users won't see this
Organization: (Optional - only if you have a Google Workspace organization)
If you see this field and have an organization, select it
If you don't have one or don't see this field, leave it blank or as default
Location: (If shown, you can usually leave this as default)
Click the blue "Create" button
Wait for the project to be created (this usually takes 10-30 seconds)
Make sure your new project is selected:
Look at the project dropdown again at the top
It should now show your newly created project name
If it doesn't, click the dropdown and select your project from the list
You'll know it worked when: You see your project name displayed in the top bar, and the dashboard shows "No resources to display" or general project information.
Step 3: Enable Required APIs
What you're doing: Turning on Google's "People API" which allows your job portal to access basic user information (like name and email) when someone logs in with Google.
Think of it like this: APIs are like switches - you need to flip the switch "on" for the features you want to use.
Look at the left side of the screen for a hamburger menu (three horizontal lines) - click it if the sidebar isn't visible
In the left sidebar, find and click on "APIs & Services"
Click on "Library" (under the APIs & Services section)
You'll see a search box at the top - type: Google People API
Click on "Google People API" from the search results
Click the blue "Enable" button
Wait for the API to be enabled (this usually takes just a few seconds)
You'll know it worked when: You see "API enabled" with a green checkmark, and the "Enable" button changes to "Manage" or "Disable."
Why this matters: The People API lets your job portal access basic profile information (name, email, profile picture) from users who log in with Google. Without enabling this, the login won't work.
Step 4: Set Up OAuth Consent Screen
What you're doing: Creating the screen that users will see when they click "Sign in with Google." This screen tells users what information your job portal wants to access and asks for their permission.
Think of it like this: This is like creating a permission slip that users will see before logging in - it explains what you're asking access to and why.
In the left sidebar, go to "APIs & Services" → "OAuth consent screen"
Choose your User Type:
Select "External" (this allows anyone with a Google account to log in)
Click the blue "Create" button
Fill in the App Information (Page 1 - App Information): App name:
Enter your job portal or company name
Example: "JobSphere Job Portal" or "YourCompany Careers"
This is what users will see when they log in, so make it professional
User support email:
Select your email from the dropdown (usually your logged-in Google account)
This is where users can contact you if they have questions
App logo: (Optional but recommended)
Click "Choose File" and upload your company logo
Recommended size: 120x120 pixels (Resize here)
This makes the login screen look more professional and trustworthy
App domain: (You might see these fields - they're optional)
Application home page: Your website homepage
Application privacy policy: Your privacy policy URL
Application terms of service: Your terms of service URL
Authorized domains:
Add your website domain (e.g., jobsphere.com)
Don't include "https://" or "www" - just the domain name
Developer contact information:
Enter your business email address
Google will use this to send you important updates
Click "Save and Continue" at the bottom
Add Scopes (Page 2 - Scopes): What are scopes? These are the specific pieces of information your job portal will access from users' Google accounts.
Click "Add or Remove Scopes"
A side panel will appear with a list of available scopes
Look for and select these scopes (check the boxes):
.../auth/userinfo.email- Email address.../auth/userinfo.profile- Basic profile info (name, picture)
If you can't find these, you can manually add them in the "Manually add scopes" field:
Type:
https://www.googleapis.com/auth/userinfo.emailType:
https://www.googleapis.com/auth/userinfo.profile
Click "Update" at the bottom of the side panel
Click "Save and Continue"
Test users (Page 3 - Test users): (Optional during development)
If you want to test the login before Google approves your app, add test email addresses here
Click "Add Users" and enter email addresses of people who can test
For now, you can skip this by clicking "Save and Continue"
Summary (Page 4):
Review all the information you entered
If everything looks good, click "Back to Dashboard"
You'll know it worked when: You see the OAuth consent screen dashboard showing your app name, status (likely "Testing" or "In production"), and the information you just entered.
Important Note: At this stage, your app will be in "Testing" mode. To go live for all users, you'll need to submit it for Google's verification (we'll cover this later).
Step 5: Create OAuth 2.0 Client ID
What you're doing: Getting your unique credentials (Client ID and Client Secret) from Google. These are like special keys that allow your job portal to securely communicate with Google.
In the left sidebar, go to "APIs & Services" → "Credentials"
At the top of the page, click "+ Create Credentials"
From the dropdown menu, select "OAuth Client ID"
Choose Application Type:
Select "Web application" from the dropdown
(Note: If you're setting up for a mobile app, you'd choose iOS or Android instead)
Fill in the details: Name:
Give this credential a name
Example: "JobSphere Web Login" or "Production Login Credentials"
This is just for your reference in the Google Cloud Console
Authorized JavaScript origins: (Optional - you can skip this section)
This restricts which websites can use these credentials
Example:
https://yourwebsite.com
Authorized redirect URIs: ⚠️ CRITICAL - Must Be Correct
Click "+ Add URI"
Enter your redirect URL in this exact format:
Important: Replace "yourwebsite.com" with your actual domain name
Make sure to include
https://at the beginningMake sure the path
/jobseekers/loginis correct for your specific setup
Examples:
If your website is jobsphere.com:
https://jobsphere.com/jobseekers/loginIf your website is careers.mycompany.com:
https://careers.mycompany.com/jobseekers/login
Click the blue "Create" button
You'll know it worked when: A popup appears showing your new credentials.
Step 6: Get Your Client ID and Client Secret
What you're doing: Copying the two special codes that Google just generated for you. You'll need to share these securely with Artha Support.
After clicking "Create" in the previous step, a popup will appear with your credentials:
Your Client ID (a long string like:
123456789-abcdefghijk.apps.googleusercontent.com)Your Client Secret (a shorter string of random characters)
Option 1 - Download JSON:
Click the "Download JSON" button in the popup
This saves a file to your computer containing both credentials
Keep this file in a secure location
Never share this file publicly or commit it to public code repositories
Option 2 - Copy Manually:
Click the "Copy" icon next to Client ID and paste it into a secure document
Click the "Copy" icon next to Client Secret and paste it into the same document
Label them clearly: "Google Client ID" and "Google Client Secret"
Click "OK" to close the popup
If you need to see these credentials again later:
Go to APIs & Services → Credentials
Under "OAuth 2.0 Client IDs" you'll see your credential
Click on the name to view the Client ID and Client Secret again
⚠️ IMPORTANT SECURITY NOTES:
The Client Secret is like a password - keep it private and secure
Don't share it publicly or post it anywhere online
Don't email it to yourself using unsecured email
Store it in a password manager or encrypted document
You'll share it securely with Artha Support Team in a later step
You'll know you have everything when: You have both the Client ID and Client Secret saved securely in a document or downloaded JSON file.
Step 7: Submit for Google Verification (Required for Public Use)
What you're doing: Asking Google to review and approve your application so that all users (not just test users) can use the "Sign in with Google" feature.
⚠️ CRITICAL INFORMATION: This step is required before your Google login can work for all users. Google's verification process typically takes 1-4 weeks (sometimes longer). Plan accordingly!
Why Google requires this: Google wants to ensure that applications using "Sign in with Google" are legitimate and won't misuse user data. This protects both users and your reputation.
Go to APIs & Services → OAuth consent screen
You'll see your app status is currently "Testing" or "In development"
Look for a button that says "Publish App" or "Submit for Verification"
Click "Publish App" or "Submit for Verification"
Google will ask you to confirm - read the information and click "Confirm"
You may need to fill out a verification questionnaire:
Explain how your application uses Google user data
Provide links to your privacy policy and terms of service
Explain your data handling and security practices
Be honest and thorough - this helps speed up approval
Submit the verification request
What happens next:
Google's team will review your application
They may email you asking for additional information or clarification
Check the email address you provided as "Developer contact information" regularly
Response time varies: typically 1-4 weeks, but can be longer during busy periods
You'll know your app is approved when:
You receive an email from Google confirming verification
The OAuth consent screen shows status as "In production" or "Published"
The "Sign in with Google" button will work for all users
Step 8: Share Information with Artha Support Team
What you're doing: Giving the Artha technical team the information they need to connect your job portal's backend to Google.
🚨 CRITICAL: You do NOT need to configure or code anything yourself. The Artha Support Team handles all technical integration.
⚠️ Important Timing Note: You can share these credentials with Artha Support now, but we won't be able to complete the integration until Google approves your application (Step 7). However, sharing early allows them to prepare.
What to send to Artha Support:
Send an email to Artha Support with the following information:
Email Address: [email protected]
Email Subject: Google Social Login Setup - [Your Company Name]
Email Body:
Security Tip: If your company uses a secure file-sharing system (like a password-protected document or encrypted email), consider using that instead of regular email for sharing the Client Secret.
Alternative Method: You can also attach the downloaded JSON file (from Step 6) instead of pasting the credentials in the email. Just make sure to use a secure method.
Step 9: Wait for Google Approval & Artha Confirmation
What you're doing: Waiting for two things: (1) Google's approval of your application, and (2) Artha Support to complete the backend integration.
Understanding the timeline:
Phase 1 - Waiting for Google Approval:
Expected time: 1-4 weeks (sometimes longer)
What's happening: Google's team is reviewing your application to ensure it meets their security and privacy standards
What you should do:
Check your developer contact email regularly (including spam folder)
Respond promptly if Google requests additional information
Be patient - this is a thorough review process
Phase 2 - Artha Support Integration:
When it happens: After Google approves your application
Expected time: 1-3 business days after approval
What's happening:
Artha team is adding your Google credentials to your job portal's configuration
They're testing the connection between your portal and Google
They're making sure the "Sign in with Google" button appears correctly
They're verifying that user data flows properly
Step 10: Test Your Google Login
What you're doing: Making sure everything works correctly before your actual job seekers start using it.
⚠️ IMPORTANT: Only proceed with testing after you've received confirmation from BOTH Google (app approved) AND Artha Support (integration complete).
Once both confirmations are received:
Go to your job seeker login page
Look for the "Sign in with Google" button
It should appear alongside other login options
It should have Google's official logo and colors
Click the button and follow the process:
You'll be redirected to Google's login page
Log in with a Google account (use a test account first, not your admin account)
You'll see the OAuth consent screen you created in Step 4
It should show your company name, logo, and the information you're requesting
Click "Allow" or "Continue"
You should be redirected back to your job portal, now logged in
Common issues and fixes:
Issue: Button doesn't appear
Solution: Google Social login must be enabled from https://yourwebsite.com/admin/settings?tab=6
Issue: Error message appears when clicking the button
Solution: Verify your redirect URL is correct in Google Cloud Console (Step 5)
Issue: Redirects to wrong page or shows error after login
Solution: Double-check your redirect URL matches exactly in both Google Cloud Console and what you shared with Artha Support
Issue: Shows "Access blocked: This app's request is invalid"
Solution: Your app might not be published yet - check OAuth consent screen status
Issue: "This app isn't verified" warning
If you see this: Your app hasn't been verified by Google yet (still in Step 7)
Troubleshooting Common Issues
"I don't see the option to create a new project"
Solution: Make sure you're logged into the correct Google account. Some Google accounts may have restrictions. Try using a Google Workspace administrator account if available.
"Google People API won't enable"
Solution: Make sure you have a project selected (check the top bar). If the issue persists, wait a few minutes and try again - sometimes Google's systems need time to process your project creation.
"I can't find the OAuth consent screen option"
Solution: First, make sure you've selected your project from the dropdown at the top. Then check that you're looking under "APIs & Services" in the left sidebar. If you still can't find it, try refreshing the page.
"My redirect URL isn't being accepted"
Common mistakes:
Missing
https://at the beginningExtra spaces before or after the URL
Using
http://instead ofhttps://(Google requires HTTPS)Wrong domain name or typo in the path
Solution: Double-check the exact URL format. It should match your actual login page URL exactly.
"Google verification is taking longer than expected"
Solution: Google's verification can take 1-4 weeks, sometimes longer during busy periods. If it's been more than 4 weeks:
Check your spam folder for emails from Google
Log into Google Cloud Console and check for notifications
If needed, contact Google Cloud Support for a status update
"Users see 'This app isn't verified' warning"
Solution: This means your app hasn't completed Google's verification process yet. During testing, users can click "Advanced" → "Go to [Your App] (unsafe)" to proceed, but for production, you must complete the verification in Step 7.
"The login button shows 'Artha' instead of my company name"
Solution: Contact Artha Support immediately - there's a branding configuration that needs to be updated on the backend. Also verify your OAuth consent screen settings in Step 4 show your company name correctly.
"Users are getting an error after clicking the Google button"
Solution:
Verify your redirect URL is correct in Google Cloud Console
Check that Google People API is enabled
Verify your app is published (not in "Testing" mode)
Contact Artha Support to check backend configuration
Take a screenshot of the error and share it with Artha Support
"I lost my Client Secret"
Solution: You can generate a new one in Google Cloud Console:
Go to APIs & Services → Credentials
Click on your OAuth 2.0 Client ID
Click "Reset secret" or create a new credential
Copy the new secret immediately
Share it with Artha Support to update the backend
"Google is asking for additional verification documents"
Solution: This is normal for some types of applications. Google may request:
Proof of domain ownership
Privacy policy details
Data handling and security documentation
Video demonstration of your application Respond to their requests promptly with clear, detailed information.
"The OAuth consent screen shows in the wrong language"
Solution: The consent screen language is based on the user's Google account language settings. You can provide translations in the OAuth consent screen settings, but the default display language is controlled by each user's Google account preferences.
Frequently Asked Questions
Q: Will this cost me anything? A: Google's basic OAuth authentication is free. There are no charges from Google for standard social login functionality.
Q: How long does Google's verification take? A: Typically 1-4 weeks, but it can take longer during busy periods or if Google requests additional information. Some applications are approved within days, while others may take 6-8 weeks.
Q: Can I start using Google login before verification is complete? A: Yes, but only in "Testing" mode with limited test users. For all users to access it, you must complete Google's verification process.
Q: What information does Google share with my job portal? A: Only what you request in the "scopes" (Step 4). Typically: name, email address, and profile photo. Users see exactly what's being shared when they authorize the login.
Q: Can users still create regular accounts with email/password? A: Yes! Google login is an additional option, not a replacement. Users can choose their preferred method.
Q: What if a user doesn't have a Google account? A: They can use your portal's regular email/password registration. Google login is optional.
Q: What happens if someone changes their Google password? A: It doesn't affect their login to your job portal. The OAuth token is separate from their Google password. They can continue logging in normally.
Q: Is this secure? A: Yes.
Last updated
Was this helpful?