Evaluate Vercel Flags from another project without sharing SDK keys.
Vercel Project Connections let one project read another project’s feature flags using deployment identity, removing the need to copy and manage server SDK keys.
**Project Connections** let projects in the same team read flags from another project. Access is read-only across environments; the consumer deployment selects the flag environment, and access can be revoked without redeploying.
For apps split across Vercel projects, connect the source project and create an adapter with its project ID. Local development uses the OIDC token retrieved by `vercel env pull`.
**Project Connections** let projects in the same team read flags from another project. Access is read-only across environments; the consumer deployment selects the flag environment, and access can be revoked without redeploying. For apps split across Vercel projects, connect the source project and create an adapter with its project ID. Local development uses the OIDC token retrieved by `vercel env pull`. The feature requires **@flags-sdk/vercel 1.6.0** or **@vercel/flags-core 1.11.0**; CLI connection management requires **Vercel CLI 63.0.0**. The material does not detail how OIDC credentials are handled locally.
This adds cross-project flag reads within a Vercel team without sharing SDK keys, with read-only access, environment selection by the consuming deployment, and revocation without redeploying. The required SDK and CLI versions make compatibility part of adoption; local OIDC credential handling remains unspecified.