1
Start in Console
Open the customer’s Your infrastructure area and start the Vercel connection. The authorization flow is bound to your current account and session.
2
Authorize the correct team
Select the customer-owned team in Vercel. Webdock verifies the returned team, installation, integration and granted scopes. The platform’s own team and a team already assigned to another customer are rejected.
3
Select projects
Choose which authorized projects Webdock may use. Changing this list requires the current connection revision and rechecks the provider’s available projects.
4
Inspect resources
Open a selected project to view the permitted deployment and domain information. Reconnect when the provider grant no longer includes the access your action requires.
Supported management actions
The connection can inspect selected projects and their resources. With the required provider write scopes, Webdock can set the project’s default Function region to Frankfurt (fra1) and cancel a deployment that is still queued, initializing or building.
Setting the default region does not move an already deployed Function. It also does not make global CDN, control-plane or logging services EU-only. Check the actual deployment after a new release.
Connecting a team is not authorization for arbitrary provider operations or an automatic application deployment. Git deployment setup is a separate flow.
Disconnect
Disconnecting removes Webdock’s stored connection. Your Vercel projects and deployments remain in the provider account. Review or revoke the provider-side installation separately if it should lose access there too.The browser uses Console, while existing registered OAuth callback addresses remain compatible. Start connection attempts in Console rather than manually changing callback hostnames.