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

# Vercel

> How DSALTA integrates with Vercel — data collected, setup guide, and automated compliance checks.

## Overview

DSALTA connects to Vercel using read-only API access to collect compliance evidence automatically. Data syncs every 24 hours and feeds into your Data Library modules.

<Info>
  **Read-only access.** DSALTA never modifies, creates, or deletes resources in your Vercel account.
</Info>

## How to Connect

Vercel connects with a Vercel **API token** — there's no app to install. Optionally add a **Team ID** to scope reads to a specific team.

<Steps>
  <Step title="What connecting means">
    DSALTA reads your Vercel resources — projects, deployments, and team members — to monitor and record statuses for security compliance. You can mark specific resources to be monitored and ignore others.
  </Step>

  <Step title="Create an access token">
    In Vercel, go to **Account Settings → Tokens** and create a token (for example, name it `DSALTA`). Copy the token — it typically starts with `vcp_`.
  </Step>

  <Step title="Find your Team ID (optional)">
    Only if you need team-scoped projects: in Vercel, go to **Team → Settings → General → Team ID** (starts with `team_`). Skip this for personal or hobby projects.
  </Step>

  <Step title="Connect">
    In the DSALTA sidebar, go to **Integrations**, find **Vercel**, and click **Connect**. Paste your access token (and optional Team ID) into the secure window and submit.
  </Step>

  <Step title="Finish">
    DSALTA verifies the token and completes an initial sync, after which the compliance checks below activate.
  </Step>
</Steps>

## Automated Compliance Checks

Each check below runs automatically every 24 hours. Click any check for step-by-step remediation guidance.

| Check                                                                                                                  | Description                                                                 |
| ---------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| [User access to Critical System should be valid](/integrations/vercel/user-access-to-critical-systems-should-be-valid) | Checks that users with access to critical systems are authorized in Vercel. |
| [Offboarded users should not have active access](/integrations/vercel/offboarded-users-should-not-have-active-access)  | Checks that offboarded employees no longer retain active Vercel access.     |

## Troubleshooting

<AccordionGroup>
  <Accordion title="Integration shows Disconnected">
    Re-authenticate from **Integrations → Vercel → Reconnect**. This can happen if the access token was revoked or deleted in **Vercel → Account Settings → Tokens**.
  </Accordion>

  <Accordion title="Data is not syncing">
    Confirm the access token is still valid and, if you scoped the connection to a team, that the Team ID is correct and the token has access to that team. Then trigger a manual sync from the integration settings.
  </Accordion>
</AccordionGroup>