> ## Documentation Index
> Fetch the complete documentation index at: https://docs.webdock.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Your Vercel team

> Connect a customer-owned team and limit access to selected projects.

You need the workspace's Vercel BYOK permission and authority to install the configured integration in your Vercel team. The Webdock operator must have configured the customer integration before this flow is available.

<Steps>
  <Step title="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.</Step>
  <Step title="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.</Step>
  <Step title="Select projects">Choose which authorized projects Webdock may use. Changing this list requires the current connection revision and rechecks the provider's available projects.</Step>
  <Step title="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.</Step>
</Steps>

## 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.

<Note>The browser uses Console, while existing registered OAuth callback addresses remain compatible. Start connection attempts in Console rather than manually changing callback hostnames.</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.