Skip to content
Docs · Connections

Connections and audit

Connections and the vault

Store GitHub, AWS, Stripe, Slack, Google or custom credentials in Yomenie's vault. Secrets are encrypted, write-only and never shown again, to anyone.

Updated

On this page

A connection is a credential for a third-party service, such as an API key or an OAuth token, that your agents can be granted access to through the broker. Open Settings → Connections (the gear at the bottom of the left rail; owners and admins see it).

Owners and admins manage connections (the connections:manage action).

Adding a connection

Under Add a connection:

Field Notes
Provider GitHub, AWS, Stripe, Slack, Google, or Custom
Label Something you’ll recognise, like “GitHub · acme org” (up to 80 characters)
Type API key or OAuth token
Secret The credential itself

Press Save connection. Saving asks you to confirm it’s you.

Each provider has its own list of scopes that grants can use:

Provider Scopes
GitHub repo:read, repo:write, pr:create, pr:merge, actions:run, deploy
AWS s3:read, s3:write, logs:read, lambda:invoke, deploy
Stripe charges:read, refunds:write, customers:read
Slack chat:write, channels:read
Google calendar:read, calendar:write
Custom any (*)

Write-only secrets

“Secrets are write-only: once saved, nobody can read them back, agents included.”

  • A secret is encrypted (AES-256-GCM) as soon as it arrives, and only the ciphertext is stored.
  • No page or API response ever shows it again. Agents get short-lived tokens from the broker, never the secret.
  • It’s never logged.

Rotating and revoking

Each connection shows when it was added and by whom, when it was last rotated and used, and which agents can use it with which scopes.

  • Rotate secret: enter the new secret and press Rotate. Agents’ grants keep working.
  • Revoke: every grant on the connection stops working at once, the stored secret is deleted, and the connection disappears from the list.

Both ask you to confirm it’s you, and both are written to the audit log.