CONNECTIONS

ACCOUNT REGISTRY — WHAT JARVIS CAN ACTUALLY REACH

--:--:--
-- --- ----

J.A.R.V.I.S. · Integrations

Every outside account, in one register

Add the accounts Jarvis should know about, see which are genuinely wired up, and keep multi-account Google access in one place. Credentials never leave this machine.

Registry— Accounts— HandlingLocal · 0600
Google accounts Settings

Loading…

How credentials are handled

Write-only secrets. A Gmail app password is stored in data/connector_secrets.json with mode 600. No API route ever returns it, and the browser only ever sends it once.
Honest capability labels. “Native” means Jarvis has code that talks to it today. “Adapter pending” means the account is recorded for the roadmap, not connected — nothing will read it yet.
Per-account OAuth. Calendar, Drive and Docs use one token per Google account under data/google_tokens/. Gmail stays on an app password, because IMAP is the path that already works locally.

Nothing here is uploaded · accounts live in data/connectors.json · remove an account at any time

Add account

  1. Choose method
  2. Authorize
  3. Test
  4. Done