Browse apps, add an AI client, then run passport login to activate a profile or paste your connector URL. Credentials, workspace policy, and Activity stay in one place.
A solo developer connects GitHub, adds Passport CLI, and runs the built-in read-only setup check. Enterprise policy and team rollout stay available when the workspace grows.
Passport
Maya · Apps
GitHubPersonal accountConnected
Browse apps → Connectread-only first
Maya · Terminal
Passport CLIBrowser-confirmed sign-inConnected
passport login → active profileno token pasted
Maya · Activity
passport.activation_check→setup passed
Passport web · activation_check · allowed
Read-only · workspace policy checked · provider not contacted
1Browse appsMaya connects the account she wants to use.
2Add a clientRun passport login to activate a profile, or paste the connector URL.
3Prove the pathA safe diagnostic crosses policy and lands truthfully in Activity.
The admin audit view: every governed call attributed to a person and the AI client they used.
Connect, govern, audit.
Protect access without slowing people down.
AI clients receive scoped Passport access. Upstream credentials stay encrypted at the gateway and out of client configuration files.
Credentials protectedUpstream OAuth tokens and company keys are encrypted at rest with AES-256-GCM.
Access matched to the jobChoose what each workspace, team, person, client, and governed tool can use.
Offboarding from one placeRevoke sessions, clients, and connected-account grants centrally or through SCIM.
Useful activity, less sensitive contentAttribute governed calls without storing prompts, full arguments, or tool results in the audit trail.