Skip to main content

​
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.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Vercel account.

​
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.
1

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

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_.
3

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

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

Finish

DSALTA verifies the token and completes an initial sync, after which the compliance checks below activate.

​
Automated Compliance Checks

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

​
Troubleshooting

Re-authenticate from Integrations → Vercel → Reconnect. This can happen if the access token was revoked or deleted in Vercel → Account Settings → Tokens.
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.