How do I verify the Applane GCP setup?

Who

GCP admin for the terminal check; the Applane admin for the console check

Time

3 minutes

Confirm both the infrastructure checks and a real user workflow before handing Applane over to the team. The script is read-only in --check mode.

From the terminal

./applane-setup.sh --check --project <GCP_PROJECT_ID> --group applane-builders@<YOUR_DOMAIN>

It checks what gcloud can see and changes nothing:

Line	What it checks
PASS API enabled: ... x5	Each of the five APIs is on.
PASS IAM: roles/aiplatform.user -> group:...	The IAM grant exists.
PASS Billing linked to ...	The project has a billing account.
INFO Apps Script API user setting	Cannot be checked from here; per user.
INFO OAuth consent screen and client	Cannot be checked from here; Google has no API for it.

A FAIL line prints the command that fixes it.

From the Applane console

The Applane admin opens Setup > Run checks. The checker runs from their browser and from Applane’s backend, each checking what it can see, and stores only pass or fail.

Check	How	If it fails
Domain verified	DNS TXT lookup	The record to add. Verify your domain
Client id saved	The tenant record	Paste it. OAuth client
Test sign-in passed	The sign-in flow once, from the admin’s browser, openid email only, returning to https://admin.applane.dev/oauth-probe	The Google error, verbatim. Error messages
Five APIs enabled	Asks Google which services are on, with the admin’s token from that one sign-in	The missing API and the gcloud services enable line
roles/aiplatform.user granted	Tests the binding with the admin’s token	The gcloud projects add-iam-policy-binding line
Bot account and admin group exist	Manual: the Workspace admin ticks it	Accounts and groups

The admin’s Google token from the test sign-in is used inside their browser session and is not sent to Applane.

The per-user Apps Script API switch is not on this list. Each builder turns it on themselves at script.google.com/home/usersettings, and the builder shows them the link on first run: Apps Script API setting.

Complete the handover test

Open the builder, sign in, and build one app. Confirm the seat appears under People, test the deployed app, then publish it and ask a colleague to check access. A successful admin session alone does not prove that builders have the required permissions. Open and sign in, Your first app.