Connect Vercel

Connect Vercel to an environment so its project and deployment context can contribute to reviews.

Connect through Vercel#

An organization administrator connects Vercel. When Connect through Vercel is available on the Vercel connection page, you can authorize projects without entering an API token.

  1. Open Settings → Connections → Vercel and select Connect through Vercel. You can also start from Proofline's Vercel installation link.
  2. In Vercel, choose the account or team and authorize the projects Proofline may read.
  3. Sign in to Proofline with GitHub if prompted, then choose the Proofline organization.
  4. Select Continue to projects to check the Vercel authorization.
  5. Choose a Vercel project and Proofline environment, then select Connect project.
  6. Select Return to Vercel, or open Proofline connections to continue setup.

Vercel's project permissions limit access. The project and environment choices in Proofline determine which authorized project each environment reads.

Connecting a project queues evidence synchronization. It does not mean evidence is ready. Existing Proofline credits and billing apply; connecting Vercel does not start a paid review.

If GitHub setup is not complete, install the GitHub App and select Reload organizations. If no environment exists, use Create a Proofline environment and return to finish the connection. An expired authorization requires you to start Vercel setup again.

Add the connection#

Use an API token when you prefer the manual connection or Connect through Vercel is unavailable.

  1. Open Settings → Connections.
  2. Select Connect Vercel.
  3. Select the environment and enter the Project ID.
  4. Enter the Team ID if the project belongs to a team.
  5. Enter an API token scoped to that project or team.
  6. Select Connect and check the result.

Use access scoped to the Vercel team and projects you intend to connect. Keep the token out of repository files and support messages.

Check the scope#

Inspect the connection's environment and team details. A connection to one environment does not automatically establish the context for another environment.

Each environment holds one Vercel project connection.

Link to a GitHub repository records an explicit repository declaration. It does not attest which code Vercel built. Deployment commit metadata remains unverified, and deployment readiness does not establish application health.

The integration requests read access to its installation, projects and deployments. Vercel's permissions can cover more data than Proofline collects. Proofline does not collect environment-variable values or build logs through this connection.

Inspect evidence or remove access#

Open the environment's Evidence page to inspect collection results. Connection setup and evidence coverage are separate checks.

Use the connection's removal action when Proofline should stop using it. Read the confirmation and check the final state after removal.

For a Marketplace installation, Manage projects reopens project mapping. Disconnect installation stops all project connections under that installation in Proofline. Uninstalling the integration in Vercel also withdraws its access. Removing a project from Vercel's authorized selection stops that project's connection. Historical reviews remain available under the existing retention policy.

Search help

Tab to a result. Enter to open. Escape to close.