Two distinct sharing patterns:
  • Wrapping — hand a single secret to another caller once, with tamper evidence.
  • Cross-workspace grants — expose specific paths to another workspace inside the same organisation.

Wrapping

Producer wraps a secret into a one-time-use token:
WRAP=$(vault kv get -wrap-ttl=60s secret/prod/api-key -format=json | jq -r .wrap_info.token)
Send WRAP over the least-trusted channel available — Slack, email, a git commit message. Consumer unwraps once:
vault unwrap "$WRAP"
If the token was already unwrapped, the second unwrap fails and you know the channel was compromised. Inspect a wrap without consuming it:
vault wrapping lookup "$WRAP"
# → { creation_time, creation_path, creation_ttl }

Cross-workspace grants

Grants are a TigerTrust extension on top of the Vault-compat surface. An organisation admin can expose specific paths from one workspace to another (useful for a shared-services team publishing to product teams). Settings → Secrets Manager → Sharing → New grant. Pick source workspace, target workspace, path pattern, capabilities (read / list), and TTL. The consumer workspace sees a virtual mount at the same path with the granted capabilities. Grants are audited on both sides.

Secrets

Reading, writing, and versioning.

Policies

Which policies apply to granted paths.