Vercel replaced its Sensitive toggle with Config and Secret environment variable types
As of 2026-08-24, adding or editing a Vercel environment variable means choosing Config or Secret instead of flipping a Sensitive toggle. Config values stay readable after saving for members with access, for things like public framework settings you may need to inspect later; Secret values remain usable by deployments and updatable but are never viewable again, for passwords, API keys and tokens. Existing sensitive variables auto-converted to Secrets with no migration work. The 'Enforce Sensitive Environment Variables' policy is deprecated in favor of a new 'Separate Production Secret Values' policy requiring production Secrets to differ from preview, development, and custom environments. CLI support is the --visibility flag on vercel env add and vercel env update.
↳ Follow the thread