Connect Vercel

1. 01

   Connect Vercel

   From Connections, install or authorize the Sentrail Vercel integration for the intended personal account or team.
2. 02

   Choose the deployment

   Select the Vercel project that deploys this Sentrail project's application.
3. 03

   Refresh posture

   Run the deployment check to collect the current project, environment-key, domain, deployment, and protection signals.

• Environment variable names, target environments, and Vercel variable types.
• Names that use public client prefixes while appearing secret-like.
• Configured and verified domains.
• Latest deployment URL, state, target, and creation time.
• Available password, SSO, and deployment-protection signals.

A public prefix is not automatically a vulnerability. It means the variable may be bundled into client code and should not contain a credential. Review the key's purpose and the application code that consumes it.

Protection posture also depends on intent. A public production site may not need password protection, while previews, internal tools, and administrative surfaces often should not be broadly reachable.

• If the project list is empty, confirm the integration was installed for the correct Vercel account or team.
• If a token expired, reconnect Vercel so the OAuth flow can restore access.
• If posture is stale, refresh the connection after changing environment variables, domains, or protection settings.
• If Vercel is not part of the stack, leave it disconnected rather than linking an unrelated deployment.