Introduction #

DriveHub allows you to connect your Google Drive account in two different ways.

• Automatic Connection – Connect instantly using DriveHub’s shared Google application. No Google Cloud setup is required.
• Manual Connection – Connect using your own Google Cloud project and OAuth credentials. This gives you full control over your integration and uses your own API quota.

The Manual Connection method is recommended if you want to:

• Use your own Google Cloud project
• Keep your API quota separate from other DriveHub users
• Connect DriveHub for your business or organization
• Have full ownership of your Google Drive integration

This guide will walk you through every step of the setup process.

---

Before You Start #

Open your WordPress dashboard and navigate to:

DriveHub → Accounts → Manual

Keep this page open in a separate browser tab. You’ll need to copy the Redirect URI later in the setup.

---

Step 1: Open Google Cloud Console #

Open a new browser tab and visit:

https://console.cloud.google.com

Sign in with the Google account that owns the Google Drive you want to connect.

If you’re already signed in with a different account, switch to the correct one before continuing.

---

Step 2: Create a Google Cloud Project #

Click the project selector at the top of the Google Cloud Console.

Select New Project.

Enter a project name, such as DriveHub, then click Create.

After the project is created, open the project selector again and make sure your new project is selected before moving to the next step.

Tip: All APIs, credentials, and settings you create will belong to the currently selected project.

---

Step 3: Enable the Google Drive API #

From the left sidebar, go to:

APIs & Services → Library

If the sidebar is hidden, click the menu icon in the upper-left corner.

Search for:

Google Drive API

Open the API page and click Enable.

Wait a few moments until Google finishes enabling the API.

---

Step 4: Configure the OAuth Consent Screen #

From the left sidebar, navigate to:

APIs & Services → OAuth consent screen

Choose a User Type #

Select one of the following options:

• External if you’re using a personal Google account or your app will be available to anyone.
• Internal if you’re using Google Workspace within your organization.

Click Create.

Enter Your App Information #

Fill in the required fields:

• App name
• User support email
• Developer contact email

You can leave the optional fields empty.

Click Save and Continue.

Add the Required Scopes #

On the Scopes page, click Add or Remove Scopes.

Search for and select the following scopes:

• Google Drive (.../auth/drive)
• User Email (.../auth/userinfo.email)
• User Profile (.../auth/userinfo.profile)

Click Update, then click Save and Continue.

Add a Test User #

On the Test Users page, click Add Users.

Add the Google account you’ll use to connect DriveHub.

Click Save and Continue, then click Back to Dashboard.

Note: If your app hasn’t been verified by Google yet, only Test Users can authorize the application.

---

Step 5: Create an OAuth Client ID #

Go to:

APIs & Services → Credentials

Click Create Credentials and choose OAuth Client ID.

If Google asks you to complete the OAuth Consent Screen first, finish that setup before returning to this step.

For the application type, select:

Web Application

Enter any name for your OAuth client, such as DriveHub Website.

Before creating the client, you’ll need to add your Redirect URI.

---

Step 6: Add the Redirect URI #

Return to your WordPress dashboard.

Go to:

DriveHub → Accounts → Manual

Locate the Redirect URI field and copy its value.

Go back to Google Cloud Console.

Under Authorized Redirect URIs, click Add URI and paste the copied Redirect URI.

Make sure the URL:

• Starts with https://
• Matches the DriveHub Redirect URI exactly
• Does not contain extra spaces
• Does not include additional or missing slashes

When you’re finished, click Create.

Important: Even a small difference between the two Redirect URIs can prevent Google authentication from working.

---

Step 7: Connect DriveHub to Google Drive #

After creating the OAuth client, Google will display your:

• Client ID
• Client Secret

Copy both values.

Return to:

DriveHub → Accounts → Manual

Paste:

• The Client ID into the App Client ID field
• The Client Secret into the App Secret Key field

Click Connect with Google.

A Google sign-in window will open.

Choose your Google account, review the requested permissions, and click Allow.

Once authorization is complete, DriveHub will be connected to your Google Drive account.

---

Step 8: Understanding the “Google hasn’t verified this app” Warning #

If you’ve just created your Google Cloud application, Google may display a warning saying:

Google hasn’t verified this app.

This is expected for newly created applications.

If You’re Only Testing #

Click:

1. Advanced
2. Go to Your App Name (unsafe)

Continue the sign-in process.

Because you added yourself as a Test User earlier, Google will allow you to continue.

If You’re Releasing Your Website Publicly #

If other users need to connect their own Google Drive accounts, you’ll need to verify your application with Google.

Open:

Google Cloud Console → OAuth Consent Screen → Verification Center

Google may ask you to provide:

• A Privacy Policy URL
• A Homepage URL
• A short video demonstrating how your application uses Google Drive
• Additional information about your application

The review process typically takes several days.

---

Troubleshooting #

Redirect URI Mismatch #

If you receive a redirect_uri_mismatch error, the Redirect URI configured in Google Cloud does not exactly match the one provided by DriveHub.

Check for:

• HTTP instead of HTTPS
• Extra or missing slashes
• www versus non-www
• Typing mistakes

Update the Redirect URI and try connecting again.

---

Invalid Client ID or Client Secret #

If DriveHub reports that your credentials are invalid:

• Copy both values again from Google Cloud Console.
• Make sure you copied the complete values.
• Remove any extra spaces before or after the credentials.
• Confirm you’re using the credentials from the correct Google Cloud project.

---

Google Doesn’t Show the Consent Screen #

If Google displays an error instead of the consent screen, verify that:

• The Google Drive API is enabled.
• The OAuth Consent Screen has been completed.
• Your OAuth Client is configured as a Web Application.
• The Redirect URI matches the one shown in DriveHub.

---

You’re All Set! #

Your Google Drive account is now connected using your own Google Cloud application.

DriveHub will use your personal Google Cloud credentials for authentication and API requests, giving you full control over your integration and keeping your API usage independent from other DriveHub users.