Project-scoped Tokens
Vercel tokens can now be restricted to one project, giving agent jobs and automation read/write access without exposing unrelated project, team, or user resources.
Vercel now supports **project-scoped access tokens** for its API. A token can read and write resources only within its selected project; requests targeting other projects or user- and team-level resources are denied.
Use these tokens for coding agents, CI jobs, and deployment tools that operate on a single project. This narrows the impact of a leaked or misused credential compared with broader account credentials.
Vercel now supports **project-scoped access tokens** for its API. A token can read and write resources only within its selected project; requests targeting other projects or user- and team-level resources are denied. Use these tokens for coding agents, CI jobs, and deployment tools that operate on a single project. This narrows the impact of a leaked or misused credential compared with broader account credentials. You must choose the owning team, project, and **expiration** when creating the token. The resulting secret **is shown only once**, so its storage and rotation still need deliberate handling.
This adds a credential boundary alongside the prior runtime and sandbox boundaries: single-project agents, CI, and deployers no longer need team-wide authority. It reduces cross-project exposure but does not solve secret lifecycle management, because ownership, expiry, one-time capture, storage, and rotation remain explicit operational responsibilities.