How DSALTA integrates with Vercel — data collected, setup guide, and automated compliance checks.
Overview
How to connect
Automated checks
Useful links
DSALTA connects to Vercel using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules. Compliance checks re-run once a day at 02:00 America/New_York.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Vercel account.
DSALTA reads the Vercel team member roster — names, emails, roles and join dates, which appears on your Access page. Vercel’s members list reports no account status, so every member is listed as Active, and the roster is read only when a Team ID is configured — without one, the connected account owner is the single row and is always labelled owner; and your Vercel resources, which appear on your Inventory page.It calls these Vercel endpoints:
/v2/user
/v2/teams
/v2/teams/{teamId}/members
/v9/projects
/v5/domains
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Vercel environment.
There is no Reconnect button. Open Integrations → Connected, click Manage on the Vercel card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Vercel. This can happen if the access token was revoked or deleted in Vercel → Account Settings → Tokens.
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 click Sync from integrations on the Integrations page (Connected tab) — it refreshes every connected integration at once.
Use a Vercel API token (vcp_…). Add Team ID (team_…) only to scope reads to a specific team; leave empty for personal/hobby projects.Before you begin
Vercel account with admin access
You will need:
Field
Where to find it
Example
Access token
Create at Vercel → Account Settings → Tokens. Tokens typically start with vcp_. · Open
vcp_…
Team ID (optional)
Optional. Team → Settings → General → Team ID. Omit to use your personal account projects only. · Open
team_… (leave empty for personal)
1
Start in DSALTA
Open Integrations in the DSALTA sidebar, find Vercel, and click Connect to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below.
2
Integrating Vercel with DSALTA means
DSALTA will only be able to read your Vercel resources — projects, domains and team members — to monitor and record statuses for security compliance.Every project and domain the token can reach is synced, and each sync replaces the previous list for this integration — so deleting an asset on the Inventory page is undone by the next sync. Narrow coverage at the credential instead: scope the token, and the Team ID you enter, to the team whose resources DSALTA should read.
Team ID (optional): Only if you need team-scoped projects — Team → Settings → General → Team ID (team_…). Skip for personal/hobby.
On the Create Token form, set Scope to the team whose projects you want DSALTA to read — pick your personal account only for hobby projects. A token scoped to your personal account will not return a team’s projects, members, or deployments, so the scope you choose here has to match the Team ID you enter later.
Set an Expiration on the same form, and copy the token before you leave the page — Vercel shows the value only once. Note the expiry date too: when the token lapses the integration drops to Disconnected and you have to create a new token and connect again.
The team roster only exists on a paid plan. Vercel states that “Collaborating with other members on projects is available on the Pro and Enterprise plans” — a Hobby account has no team, so leave Team ID empty and expect your own account to be the single row on the Access page.Fastest way to the Team ID: open https://vercel.com/teams/<your-team-name>/settings#team-id. Vercel documents that route, and the fallback path if it does not jump for you: “Open your team’s dashboard and head over to the Settings section in the sidebar”, “Choose General”, “Scroll down to the Team ID section and your Team ID will be there ready for you to copy”. The ID is “unique and unchangeable” once the team is created.
4
Enter access token
Paste the token into Access token, and if you are scoping to a team, the Team ID into Team ID (optional). Leave Team ID empty for a personal or Hobby account.
DSALTA validates the credential when you click Connect. On success the integration moves to the Connected tab, and Manage → Status reads Connected and working properly. Checks begin reporting after the first sync.
If the connection is rejected. Invalid access token or insufficient permissions for the chosen scope.The on-screen message is generic — see Connection error messages.
Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)
