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

# Connect your Vercel team

> Authorize a customer-owned Vercel team and select permitted projects.

> [!NOTE]
>
> This flow requires separate Vercel integration activation and workspace permission. Native activation is separate release work; do not assume every Console workspace can connect Vercel. Ask your operator to confirm availability.

You need authority to install the configured integration in the customer-owned Vercel team.

**1. Start the connection**

Where enabled, open **Your infrastructure** in Console and choose **Connect Vercel**. Start a fresh flow from Console so it is bound to your current account and session.

**2. Authorize the correct team**

Select your team in Vercel. Spitzli Cloud verifies the returned team, installation and permissions. The platform's team and a team already assigned to another customer are rejected.

**3. Choose projects**

Select the authorized projects Spitzli Cloud may use. Changing the selection rechecks current provider access.

**4. Inspect resources**

Review the permitted deployment and domain information. Reconnect if the provider grant no longer covers the access you need.

## Available management

The integration supports selected-project inspection. With the required write permissions, it can set the default Function region to Frankfurt (`fra1`) and cancel a deployment that is still queued, initializing or building.

Changing the default region does not move an existing deployment. It does not establish EU-only CDN, logging or control-plane processing. Check the actual deployment after your next release.

Connecting a team does not deploy an application or authorize arbitrary Vercel operations. Repository deployment setup is separate, and Vercel retains your provider charges and quotas.

## Disconnect

Disconnecting removes the stored Spitzli Cloud connection. Vercel projects and deployments remain in your account. Revoke the provider-side installation separately if it should lose access there too.

> [!NOTE]
>
> Registered callback URLs remain compatibility contracts. Start authorization from Console; do not manually replace callback hostnames.


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