Secrets

Store credentials once, encrypted, grant them to the agents, routines and connectors that need them, and review proposed changes.

Veyra Docs TeamUpdated 1 min readVersion 2 · History

Secrets hold credentials (API keys, tokens, passwords) so that agents can use them without anyone pasting them into a task. A secret is stored encrypted, and its value is delivered only to the runs you granted it to.

Organization and personal secrets

  • Organization secrets belong to the organization and are granted to agents, routines or environments.
  • Personal secrets belong to one member, for credentials that must act as that person.

Add a secret

You need the Manage secrets permission (secrets:manage).

  1. Open Settings › Secrets and select New secret.
  2. Give it a key, for example STRIPE_API_KEY, and paste the value.
  3. Save. The value is never shown again; you can replace it with a new version.

Grant a secret

Grant a secret where it is used:

  • On an agent's Secrets & variables tab, to deliver it to that agent's runs.
  • In a routine's environment, to deliver it only to that routine's runs.
  • In an environment's configuration.

Grants can pin a version or follow the latest. An agent that was not granted a secret cannot read it, and its value never appears in task threads, activity or run logs.

Proposals

An agent that needs a credential can propose a secret change instead of asking for the value in chat. The proposal waits in Secrets › Proposals for someone with permission to approve or decline it.

Rotation

Replace a secret's value to rotate it. Runs that start afterward get the new value; grants pinned to an older version keep it until you update them.

From the API

The API never returns secret values to people; agents read values granted to their current run. See Secrets in the API reference.

OrganizationSecretsSecurity