Skip to content

What happens to Applane apps when a builder leaves?

Who
Google Workspace admin, with the Applane admin for the seat
Time
10 minutes per person

Every app a builder made is an Apps Script project in their Drive. Deployed internal apps run as whoever opens them, so they keep working the day the builder leaves. Published external and public apps were deployed from the bot account and keep running too.

Complete the app handover before suspending or deleting the account. Coordinate Drive ownership with the person maintaining each tool, then remove building access and reclaim the Applane seat.

Before you delete or suspend the account, transfer its Drive files, including the Apps Script projects, to a person or to applane-bot@<YOUR_DOMAIN>.

  • Whole account: Directory > Users > the user > More options > Transfer data (or the transfer prompt during deletion). Choose Drive and Docs.
  • One app only: open its project from the builder or from script.google.com, use Google’s share dialog, and make another editor the owner.

applane-admins@ is already an editor on every published app, so IT can inspect them and coordinate the handover. Use the Workspace admin transfer process where owner permissions are required.

Remove the account from applane-builders@<YOUR_DOMAIN>. This drops their roles/aiplatform.user grant on the GCP project, so no more Vertex spend can be attributed to them.

Ask the Applane admin to open People in the console and choose Reclaim seat on the leaver’s row. That frees the seat for someone else immediately. If you skip this, the seat is reclaimed automatically after 60 days without a sign-in, and monthly billing counts active seats only. See People and seats.

Suspending or deleting the Google account also ends the person’s sessions: the builder cannot renew a licence without a Google sign-in, and the seat goes idle from that day.

Suspending the account already invalidates its tokens. If you keep the account active for a hand-over period but want Applane closed for them, revoke the grant under Security > API controls > Manage third-party app access, or block the seat in the console.

For AI agents: llms.txt, llms-full.txt, or any page with a .md suffix.