Connect Google Drive

A Google Drive connection lets Game Designer keep a copy of a game's design in a Drive folder: an overview, a document per system and a sheet per entity type, written again each time somebody names a version. It is your org's. See Connections for how connecting works in general.

GreenMind asks Google for the drive.file scope only. The connection can see and change the files it made itself, and nothing else in your Drive. It never reads anything back, and Drive is never the source of truth for a game.

Ways to connect

Connect, through GreenMind's app, where it is open to your org.
Use your own app: an OAuth client in your own Google Cloud project. Start at Google Cloud's credentials page; Google's guide to OAuth for web server apps explains the rest.

There is no key option.

Making your own app

Open the Use your own app dialog for Google Drive on the Connections page, and keep it open.
In the Google Cloud console, choose or create a project.
Enable the API. In APIs & Services > Library, find Google Drive API and enable it. Without it, Google refuses every call.
Set up the consent screen. In Google Auth Platform, fill in Branding (app name, support email, your home page, privacy policy and terms addresses) and choose an Audience. An app for people outside your Google Workspace is External.
Add the scope. In Google Auth Platform > Data Access, choose Add or remove scopes, and under Manually add scopes enter:
```
https://www.googleapis.com/auth/drive.file
```
Then Update and Save.
Make the client. In Google Auth Platform > Clients, choose Create client, with type Web application. Under authorized redirect URIs, add the redirect URL from the dialog, copied exactly.
Copy the client ID and client secret into the dialog and press Connect. Sign in to Google and allow it.

Scopes

https://www.googleapis.com/auth/drive.file

Google does not treat drive.file as a sensitive scope, so it does not need Google's verification process.

If it goes wrong

Only some people can connect. While the consent screen's publishing status is Testing, only the Google accounts listed as test users under Google Auth Platform > Audience can sign in, and a connection made in Testing mode typically has to be connected again after about a week. Publish the app, or add each account that will connect as a test user.
Access blocked: redirect URI mismatch. The redirect URI on the client differs from the one the dialog shows. Copy it again.
The API has not been used or is disabled. Enable the Google Drive API in the same project the client belongs to.
Needs reconnecting. Google no longer accepts the credentials, for example because access was removed in the Google account's security settings. Reconnect.