Google Auth Platform

Google Cloud Setup Values

Use these exact values when configuring Tether's OAuth consent screen, app domain links, and OAuth client redirect URI.

Application nameTether
Application home pagehttps://llewellyn500.github.io/obsidian-tether/
Privacy policyhttps://llewellyn500.github.io/obsidian-tether/privacy.html
Terms of servicehttps://llewellyn500.github.io/obsidian-tether/terms.html
Authorized domainllewellyn500.github.io
Authorized redirect URIhttps://llewellyn500.github.io/obsidian-tether/oauth/callback.html
Logo filehttps://llewellyn500.github.io/obsidian-tether/assets/tether-google-cloud-logo.png
Scopeshttps://www.googleapis.com/auth/drive https://www.googleapis.com/auth/drive.metadata.readonly openid email

1. Add branding

In Google Auth Platform, open Branding. Set the app name, support email, logo, homepage, privacy policy, and terms links.

2. Add data access

Open Data Access and add the Drive, Drive metadata, openid, and email scopes listed above.

3. Publish after testing

Keep Testing while setup is incomplete. After one successful login, publish to In production, then log in to Tether again for a fresh refresh token.

If Google requires additional verification, complete the requested Google verification steps. Publishing to production avoids the normal 7-day Testing refresh-token expiry, but unverified apps may still show Google's warning screen or user cap.

Sync Direction

After a user selects a folder, Tether starts with a push from the local vault. Each time Obsidian opens, startup sync pulls Google Drive changes so stale devices catch up. After a plugin update, Tether pulls again before interval pushes resume. The interval timer pushes local edits back to Drive.

Folder Picker 403 Checklist

If login succeeds but Tether cannot load Google Drive folders, Google is denying the Drive API request. Check these items in the same Google Cloud project that owns the OAuth client.

  1. Open APIs & Services > Library and confirm Google Drive API is enabled.
  2. Open Google Auth Platform > Data Access and confirm the Drive, Drive metadata, openid, and email scopes are added.
  3. If the app is still in Testing, open Audience and confirm the user's Google account is listed as a test user.
  4. If scopes or tester access changed after login, log out of Tether and log in again before selecting a folder.
  5. For Google Workspace accounts, ask the workspace admin whether third-party Drive apps are blocked.