Skip to content
Rival Enterprise

What are secrets

Secrets are credentials, API keys, and other sensitive values your administrators store securely so that functions and connectors can authenticate with outside systems — without a builder ever typing a password or key directly into a script.

How secrets work

Section titled “How secrets work”
  • Stored centrally — administrators add secrets in one secure location rather than each builder managing their own copies.
  • Referenced, never exposed — builders select a secret by name when configuring a function or connector. The underlying value is never shown or copied into the function’s code.
  • Scoped access — administrators control which functions and connectors are allowed to use a given secret, so access stays limited to what is actually needed.

Why secrets matter for enterprise teams

Section titled “Why secrets matter for enterprise teams”
  • No hardcoded credentials — removing the temptation to paste an API key into a function closes off one of the most common sources of accidental credential leaks.
  • Easy rotation — if a key or password changes, an administrator updates it once and every function or connector referencing it keeps working without edits.
  • Consistent audit trail — because secrets are managed in one place, it is straightforward to see which secrets exist and what they are connected to.

A quick example: connecting to an internal API

Section titled “A quick example: connecting to an internal API”
  1. Admin adds the secret — an administrator stores an internal API key as a secret.
  2. Builder references it — when building a function that calls that API, the builder selects the stored secret from a list instead of typing in the key.
  3. The key rotates, nothing breaks — when the API key changes later, the administrator updates the stored secret once and the function keeps working with no code changes.
Section titled “Related”