# Vercel (/docs/integrations/vercel) Trace connects to Vercel through Vercel's native integration framework. You install Trace from your Vercel team and grant the integration **read-only** access to your account, so it can inventory your projects, domains, and deployments. How it works [#how-it-works] 1. From **Settings → Integrations → Cloud → Vercel** in the dashboard, click **Connect Vercel**. You'll be redirected to Vercel's install flow. You'll need an Owner or Member role on your Vercel team — other roles won't see the team's projects in Vercel's install flow. 2. Choose the Vercel team / account you want to connect and approve the requested scopes (read-only to integration configuration, projects, domains, and deployments). 3. After redirect, Trace verifies the install and begins syncing inventory: active projects, domains, and deployments. 4. The integration page shows current inventory counts and the last sync time. You can connect multiple Vercel installations to a single Trace organization. What Trace sees [#what-trace-sees] Trace requests **read-only** scopes from Vercel: * `read:integration-configuration`, confirms the integration is installed * `read:project`, lists your Vercel projects * `read:domain`, lists domains attached to those projects * `read:deployment`, lists deployments per project We do not request write scopes for project, domain, or deployment data. Disconnecting from Trace or uninstalling from Vercel revokes access immediately. Why connect Vercel [#why-connect-vercel] Source code alone can't tell you which of your deployments are actually live and internet-facing. Connecting Vercel lets Trace see your real surface (active projects, the domains attached to them, and their deployments), so that during a penetration test it works from your real, reachable footprint rather than an assumption about it. All access stays read-only; Trace never modifies your Vercel account.