Google Drive setup
Velocity Bridge reaches Google Drive through a Google Cloud client that you own. It takes about ten minutes, once, and afterwards your files travel only between your PC and Google, through an app nobody else controls.
How it works
Velocity Bridge connects to Google Drive through your own Google Cloud client. You create it once in Google Cloud Console, paste its client ID and secret into Velocity Bridge, and sign in with your Google account as usual.
The client belongs to you: Google shows your own app asking for access to your files, and you can review or revoke that access yourself at any time.
You need: a Google account (the one whose Drive you want, or any other) and a browser. No payment, no billing account.
1. Create a project
- Open console.cloud.google.com/projectcreate and sign in with your Google account.
- Project name: something you will recognise, for example My Velocity Bridge. The project ID under it is filled in for you; leave it.
- Parent resource / Location: leave it as No organisation. That is normal for a personal Google account.
- Click Create. Creating takes a few seconds; a notification appears at the top right when it is ready.
- Select the new project. Click the project button at the top left, next to the Google Cloud logo, and choose your new project in the list. Or click Select project in the notification.
Check the project button before every step that follows: it must show the name of the project you just created. If you have used Google Cloud before, the console often opens a different project first, and anything you set up there will not belong to your new one.
2. Enable the Google Drive API
The console opens on a busy dashboard full of products you do not need. Ignore it; the quickest route is the search bar.
- Click the wide search bar in the middle of the Google Cloud header, the one that reads "Search (/) for resources, docs, products and more" (or press the / key). Type Google Drive API and press Enter.
Use the page's own search bar, not your browser's Find (Ctrl+F): that only looks at the words already on the dashboard and will find nothing. - In the results, click Google Drive API (the one described as "Google Drive API" by Google Enterprise API, with the Drive icon). Do not pick Google Drive Activity API, Drive Labels API or Google Picker API.
- On the Google Drive API page, check that the project button at the top shows your project, then click the blue Enable button.
- After a few seconds the page changes to the API's details, with a Manage or Disable API button. That means it is enabled.
Another way: open the ☰ menu at the top left, then APIs & Services → Library. Type Google Drive API in the library's own search box, click the result, and click Enable. Or open the Google Drive API page directly, after selecting your project.
If the button says Manage instead of Enable, the API is already enabled in this project and there is nothing to do.
3. Set up the consent screen
The consent screen is what Google shows when you sign in. Its settings are under Google Auth Platform, with pages listed on the left.
- Open Google Auth Platform (or search for it in the console search bar) and click Get started.
- App information: App name anything, for example My Velocity Bridge; User support email your own. Click Next.
- Audience: External. Click Next.
Work or school account on Google Workspace? Choose Internal instead if it is offered: an internal app needs no test users and never asks you to sign in again, so you can skip step 4. On a personal Gmail account Internal is greyed out; use External. - Contact information: your email. Click Next.
- Tick that you agree to the Google API Services User Data Policy, click Continue, then Create.
- Click Data access on the left, then Add or remove scopes. Find and tick
.../auth/drive, described as "See, edit, create and delete all of your Google Drive files". Click Update, then Save.
4. Add yourself as a test user
A new app starts in Testing, where only the accounts you list can sign in.
- Click Audience on the left and scroll to Test users.
- Click Add users, enter the Google account whose Drive you want to use (and any others you will connect), and click Save.
About the weekly sign-in. Google ends a testing app's sign-ins after 7 days. When that happens, Velocity Bridge opens your browser to sign you in again the next time you connect, and carries on; it usually takes one click. To stop it altogether, see Stop the weekly sign-in below. It is optional.
5. Create the client
- Click Clients on the left, then Create client.
- Application type: Desktop app. This matters: other types are refused at sign-in. Name it anything and click Create.
- Copy the Client ID (it ends in
.apps.googleusercontent.com) and the Client secret (it starts withGOCSPX-). Google may show the secret only once, so also click Download JSON and keep the file somewhere safe.
6. Connect in Velocity Bridge
- Site Manager → New site → Protocol: Google Drive.
- Paste the Client ID and Client secret under Your Google Cloud client, give the site a name and click Save. The secret goes to Windows Credential Manager, never to Velocity's database.
- Click Sign in to Google Drive…. Your browser opens Google's sign-in.
- Google says "Google hasn't verified this app". That is your own app, so click Continue (or Advanced, then Go to My Velocity Bridge).
- Allow access to your Drive. The tab says Velocity Bridge is signed in; close it and connect.
One client can serve as many Google Drive sites and accounts as you like; add each account as a test user (step 4).
Stop the weekly sign-in (optional)
Publishing the app takes it out of Testing, so Google stops ending its sign-ins. Google asks for a few more details first.
- Click Branding on the left. Leave App logo empty (a logo makes Google require a full review).
- Under App domain, Google needs a home page and a privacy policy. If you have no website of your own, use the pages of the app you are authorising, Velocity Bridge:
- Application home page:
https://redicon.pk/velocity - Application privacy policy link:
https://redicon.pk/privacy
- Application home page:
- Under Authorised domains, click Add domain and enter the domain of those pages (
redicon.pk, or your own). Click Save. - Click Audience, then Publish app and Confirm. The status changes to In production. If the button is greyed out, hover over it to see what Google says is missing.
Google may then say the app needs verification, or that the domain is not verified. Both apply only to apps you submit to Google for review; for your own use you submit nothing, and the app keeps working.
If something goes wrong
- "Error 400: redirect_uri_mismatch": the client is not a Desktop app. Create a new one of that type (step 5).
- "Error 403: access_denied" / "has not completed the Google verification process": the account you signed in with is not a test user. Add it (step 4).
- "Google Drive API has not been used in project…": the API is not enabled in this project (step 2). It can take a minute to take effect.
- "This app is blocked" on a work or school account: your organisation's admin restricts third-party apps. Ask them to allow your client ID, or use the Internal audience inside that organisation.
- The browser opens to sign in again about once a week: that is the testing app's 7-day limit, handled for you. To stop it, publish the app (above).
To revoke access at any time: myaccount.google.com/connections, or delete the client in Google Cloud Console.