Vercel
Connect your Vercel team to Ploy to automatically discover who is in the team, what role each person holds, and to invite, change the role of, or remove team members directly from Ploy. Each Ploy connection scans one Vercel team — if your organisation has several teams, add a separate connection for each one and Ploy will still show you who is in which team.
What Ploy syncs
Every member of the connected Vercel team, including people whose invitation or access request is still pending.
Confirmed members are recorded as having access to Vercel, with their team role (Owner, Member, Developer, Security, Billing, Viewer, Viewer for Plus, or Contributor) shown as their entitlement.
The team itself appears in Ploy as a resource with its own membership, so when you connect more than one team you can still see exactly who belongs to each.
People who have accepted an invite or requested access but are not yet confirmed appear in Ploy without access — they haven't been let into the team yet.
When someone is removed from the team in Vercel, Ploy picks this up on the next scan and marks their access as revoked.
Syncing happens automatically on a regular schedule. Vercel does not expose per-project roles, MFA status, last-activity dates or licence information through the data Ploy reads, so those are not synced.
Before you begin
You need a Vercel account that is a member of the team you want to connect.
Reading the member list only requires the token's creator to be a member of the team. If you also want Ploy to invite people, change roles, or remove members, the token must be created by an Owner of the team.
Vercel access tokens act with their creator's permissions, so we recommend creating the token from an Owner account dedicated to integrations where possible.
Create an access token in Vercel
Sign in to Vercel and open your account token settings at vercel.com/account/settings/tokens.
Create a new token. Give it a recognisable name such as
ploy-integration.If Vercel asks you to choose a scope, scope the token to the team you want Ploy to scan.
If Vercel asks you to choose an expiration, choose no expiry so scans keep working without the token needing to be recreated.
Copy the token and store it somewhere safe — you'll paste it into Ploy in the next step.
Connect Vercel to Ploy
In Ploy, go to Integrations and choose Vercel.
On the first page, under Enter your Vercel access token, paste the token you created. The wizard also links to Vercel's REST API docs and the Vercel account tokens page if you need them.
Continue to the next page. Under Select the Vercel team to scan, choose your team from the dropdown — Ploy lists the teams your token can see. Ploy scans one Vercel team per connection; add another connection for another team.
Test the connection. Ploy reads a single team member to confirm the token works and the selected team is readable, then completes the setup.
Once connected, the first scan will bring in your team members shortly afterwards.
What Ploy can change in Vercel
With a token created by a team Owner, Ploy can:
Invite a person to the team by email, with a role of your choosing.
Change a member's team role between any of Vercel's eight team roles.
Remove a member from the team, which also dismisses a pending access request.
Grant and revoke team membership from the team's resource page in Ploy. Access granted this way is always the Member role — to grant any other role, use the invite flow instead.
Vercel has no way to suspend or disable a team member, so suspension is not available; removing the member is the equivalent action.
Troubleshooting
"Vercel rejected that access token. Create a new one and paste it again." — the token is invalid, revoked or was pasted incorrectly. Create a fresh token in Vercel and re-enter it.
"That access token cannot read this Vercel team. Check the token belongs to a member of the team." — the token was created by someone who is not a member of the selected team, or it was scoped to a different team.
"Vercel could not find that team. Choose your team again, then test." — the selected team no longer matches what the token can see. Re-select the team and test again.
"No Vercel team is selected. Choose your team, then test again." — the team step wasn't completed. Pick a team from the dropdown before testing.
Invites, role changes or removals fail with a permissions message — these actions require the token's creator to be an Owner of the team. Recreate the token from an Owner account and reconnect.
Someone left the team but still shows access in Ploy — removals are picked up by the next scheduled scan, so allow a little time for the change to appear.