Google Drive

Google Drive is the simplest cloud destination to set up. You'll need a Google account with Drive enabled (any personal Gmail account or a Workspace account works) and a minute or two for the OAuth flow.

Tusk requests the narrowest OAuth scope Google offers: drive.file. That scope grants access to files created or opened by the app itself and nothing else. Tusk cannot read, list, or modify any other file in your Drive. Even if Tusk wanted to, the OAuth grant you're giving Google doesn't allow it.

Multiple Google accounts

Tusk supports as many Google accounts as you want. Connect a personal account and a Workspace account, or one account per client. Each connected account shows up separately in the destination picker and can be used in as many projects as you want.

You can also use multiple accounts as destinations within a single project. Pick two different accounts in the destination picker, and Tusk will sync the project to both Drives in parallel.

Storage quota

Google Drive enforces a storage quota per account. Tusk checks quota before starting an offload and blocks the run if your source folder is larger than what's available, with a clear message about the gap. It does not check quota on every ordinary sync (too noisy), so very large incremental syncs can fail mid-run if you're close to the limit. Watch the notifications panel for any insufficient quota errors.

Folder collisions

Tusk blocks adding a Google Drive destination whose target folder already contains files from a previous offload from a different project. This prevents two unrelated projects from stepping on each other's files. If you want to reuse the folder, empty it in Drive first.

Revoking access

You can disconnect Tusk from a Google account at any time in Preferences → Accounts. You can also revoke access directly from your Google account at myaccount.google.com/permissions. The files Tusk wrote to your Drive aren't touched. They remain in your Drive folder as plain Google Drive files.