Email setup

When you connect Gmail, JobPilot can do three more things:

Match recruiter replies to your applications.
Read the sign-in codes that job boards email you while it's applying.
Send networking emails from your own address.

You connect Gmail through a Google OAuth client that you create yourself. JobPilot doesn't have a shared Google app, so your mail never goes through anyone else's, and Google doesn't need to review anything. You only do this once, and it takes about five minutes.

Create your OAuth client

In the Google Cloud Console, create a project. Then create an OAuth 2.0 Client ID and choose Web application as the type.
Under "APIs & Services", turn on the Gmail API for the project.
In JobPilot, open Settings → Email and copy the redirect URI. Add it to your OAuth client as an authorized redirect URI.
Go to Google Auth Platform → Data access and press Add or remove scopes. Search for gmail.readonly and gmail.send, tick both Gmail API rows, and press Save. The first lets JobPilot read replies and sign-in codes. The second lets it send networking emails.
Leave the app in Testing mode and add your Gmail address under Audience → Test users. You're the only user of your own project, so Google never needs to verify it. The downside is that Google signs you out of Testing-mode apps after about seven days, so expect to reconnect about once a week. Publishing the app doesn't help. Gmail access is restricted, and a published app that Google hasn't verified can't sign in at all.
Back in Settings → Email, paste the Client ID and Client secret, save, and press Connect Gmail.

What JobPilot can access

JobPilot can read your mail and send mail. It can't delete or change anything. Google's consent screen lists four permissions: gmail.readonly and gmail.send do the work, and openid and email only tell JobPilot which address you connected.

Your client ID and secret are encrypted and stored with your account. The secret stays on the server and is never sent to your browser. The connected Gmail account is linked to your profile and nobody else's.

Troubleshooting

"Access blocked: app has not completed the Google verification process". Your Gmail address isn't on the test users list. Add it under Audience → Test users.
403 "Request had insufficient authentication scopes". One of the Gmail permissions is missing. Add both under Data access, then disconnect and connect again in Settings → Email so Google issues a new token.
Gmail connects, but networking can't send. You connected before adding gmail.send. Add it under Data access, then press Reconnect to enable sending in Settings → Email.
Google shows a 500 error after you published the app. Published apps that use Gmail need Google's review. Switch back under Audience → Publishing status → Back to testing.

Gmail is the only email provider for now. Outlook and IMAP are planned.

Next: Credentials, so the agent can sign in to job boards.

Email setup

When you connect Gmail, JobPilot can do three more things:

Match recruiter replies to your applications.

Read the sign-in codes that job boards email you while it's applying.

Send networking emails from your own address.

Create your OAuth client

In the Google Cloud Console, create a project. Then create an OAuth 2.0 Client ID and choose Web application as the type.

Under "APIs & Services", turn on the Gmail API for the project.

In JobPilot, open Settings → Email and copy the redirect URI. Add it to your OAuth client as an authorized redirect URI.

Go to Google Auth Platform → Data access and press Add or remove scopes. Search for gmail.readonly and gmail.send, tick both Gmail API rows, and press Save. The first lets JobPilot read replies and sign-in codes. The second lets it send networking emails.

Leave the app in Testing mode and add your Gmail address under Audience → Test users. You're the only user of your own project, so Google never needs to verify it. The downside is that Google signs you out of Testing-mode apps after about seven days, so expect to reconnect about once a week. Publishing the app doesn't help. Gmail access is restricted, and a published app that Google hasn't verified can't sign in at all.

Back in Settings → Email, paste the Client ID and Client secret, save, and press Connect Gmail.

What JobPilot can access

Troubleshooting

"Access blocked: app has not completed the Google verification process". Your Gmail address isn't on the test users list. Add it under Audience → Test users.

403 "Request had insufficient authentication scopes". One of the Gmail permissions is missing. Add both under Data access, then disconnect and connect again in Settings → Email so Google issues a new token.

Gmail connects, but networking can't send. You connected before adding gmail.send. Add it under Data access, then press Reconnect to enable sending in Settings → Email.

Google shows a 500 error after you published the app. Published apps that use Gmail need Google's review. Switch back under Audience → Publishing status → Back to testing.

Gmail is the only email provider for now. Outlook and IMAP are planned.

Next: Credentials, so the agent can sign in to job boards.