Vercel shared variables

Team-wide variables on Vercel, reaching every project they are linked to.

Connection

What	This provider
Vendor	Vercel
Key	`vercel-shared-env`
Availability	`available`. You can connect it today.
Credential we hold	`vercel-token`
Values read back	yes
Activation	`on-next-deploy`

Direction	What it does
`import`	We read names and values out of the store into your environment.
`export`	We write names and values from your environment into the store.

on-next-deploy. A new value waits there and arrives with your next deploy.

Direction	Policies you can pick
`import`	`skip_existing`, `new_version`, `fail`
`export`	`create_only`, `overwrite`, `overwrite_and_prune`

How syncs work says what each one does.

Paste a credential from the vendor. We seal it and never show it again.

Field	Label	Kind	Required	What it is
`token`	Access token	secret; we mask it here and seal it	yes

You set these when you connect. Every mapping on the connection shares them.

Field	Label	Kind	Required	Advanced	What it is
`teamId`	Team ID	text	no	yes	Only for a team account. Leave empty to use the token's own scope.

You answer these once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`target`	Deployments	choice	yes	no	Which deployments read these variables. A new one reaches a project once you link it in Vercel. One of Production, Preview, Development.

We probe for these when we verify the connection.

Permission	Directions	Blocking	Without it
`user:read`	every direction	yes	We cannot confirm which Vercel account this token belongs to.
`projects:read`	every direction	yes	Preview cannot confirm the token reaches this account.
`shared-env:read`	`import`	yes	Import cannot read the team's variables.
`shared-env:write`	`export`	yes	Export cannot write anything.