Vercel

Configuring Vercel integration

Tidal Control's Vercel integration monitors your deployment platform's security configuration for compliance purposes.

What this integration monitors:

• Teams: SAML enforcement
• Team members: Confirmation status and provisioning origin
• Project members: Admin privilege configuration
• Projects: Deployment protection settings
• Environment variables: Encryption (no plain text secrets)
• Deployments: Production deployments from Git only
• Firewall: Web Application Firewall status
• Domains: Verification status and auto-renew configuration
• Certificates: Auto-renew configuration

Requirements:

• Super User role in Tidal Control
• Vercel account with access to account or team settings

Configuration step-by-step plan

What we're going to do: We'll create a Vercel access token, then add the connection in Tidal Control. If your Vercel account uses teams, you'll also provide the team ID to scope monitoring to a specific team.

Configuration steps:

1. Create an access token
2. Find your team ID (if applicable)
3. Configure the integration in Tidal Control

Step 1: Create an access token

• Log in to your Vercel account
• Click your profile picture in the top-right corner
• Select Account Settings (or navigate to Settings from the dashboard)
• Navigate to Tokens in the left sidebar
• Click Create
• Enter a name (e.g. Tidal Control)
• Select a scope: choose Full Account or the specific team you want to monitor
• Set an expiry date (optional but recommended)
• Click Create Token
• Copy the token value — it is only shown once

Step 2: Find your team ID (if applicable)

If your Vercel account uses teams and you want to scope the integration to a specific team:

• Navigate to the team's Settings in Vercel
• Go to General
• Copy the Team ID shown on this page (starts with team_)

If you created the token with full account scope, you can leave the team ID blank to monitor all teams.

Step 3: Configure the integration in Tidal Control

• Go to Settings → Integrations in Tidal Control
• Click the plus icon next to Vercel
• Fill in the configuration:
  • Name: A descriptive name, e.g. Vercel
  • Access Token: The access token from step 1
  • Team ID (optional): The team ID from step 2, if you want to scope monitoring to a specific team
• Click "Create" to save the integration

Configuration fields explained

Name:

• A descriptive name for this connection
• For example: Vercel, Vercel Production

Access Token:

• Your Vercel personal access token
• Created in step 1
• Keep this value secure

Team ID (optional):

• Scopes the integration to a specific Vercel team
• Leave blank to monitor all teams accessible to the access token
• Must start with team_

Verification

Check integration status:

• Settings → Integrations shows "Connected" status for Vercel
• Vercel tests are available in the Tests section
• Test refresh delivers results without authentication errors

Frequently asked questions

Can I use the same access token for multiple Tidal Control environments? Yes, the same access token can be used across different Tidal Control instances.

What is the difference between using a team ID and not using one? Without a team ID, the integration monitors all resources accessible to the access token. With a team ID, monitoring is scoped to that specific team.

Do I need a Vercel Pro or Enterprise plan? Some features — such as SAML enforcement and advanced deployment protection — are only available on Pro or Enterprise plans. The integration will still work on the Hobby plan, but those tests may not return any results.

Common problems

"Access Token is required"

• Make sure you entered the token value and not the token name

Tests show authentication errors after connecting

• Verify the access token is still valid — tokens can expire or be revoked in Vercel's token settings
• Check that the token scope includes the team you are trying to monitor

"VERCEL_TEAMS_SAML_ENFORCED" test fails for all teams

• SAML is an Enterprise feature in Vercel — this test will fail if your plan does not support it
• If you have Enterprise, enable SAML enforcement in the team's Security settings

No environment variable tests run

• Environment variables are only checked for non-system-generated variables
• Ensure your projects have manually created environment variables configured

Still can't figure it out?

Send an email to support@tidalcontrol.com, and we'll get back to you as soon as possible.