Account, Team & Project (CLI)

Authentication, switching teams, tokens, and project-level commands in the Vercel CLI.

These commands manage who you are acting as and which project you're operating on, rather than deployments themselves.

Authentication

vercel login      # sign in (opens a browser / email flow)
vercel logout     # sign out
vercel whoami     # print the currently authenticated user

Teams and scope

A Vercel account can belong to multiple teams. The active scope determines which team's projects you're working with.

vercel teams ls            # list teams you belong to
vercel teams invite <email>
vercel switch              # interactively change the active team scope
vercel switch <team-slug>  # switch directly

You can also override scope per command with the global --scope <slug> flag (see CLI overview).

Tokens

Tokens authenticate non-interactive environments like CI. Create and manage them in the dashboard; pass one with --token:

vercel tokens ls
vercel deploy --prod --token="$VERCEL_TOKEN" --yes

Treat tokens like passwords — store them as CI secrets, never commit them.

Project commands

vercel project ls          # list projects in the current scope
vercel project add <name>  # create a project
vercel project rm <name>   # remove a project

`vercel link`

Associates the current directory with a project, writing a .vercel/ directory (which holds project.json containing the project and org IDs). Required before project-scoped commands.

vercel link
vercel link --yes

The orgId in .vercel/project.json is also where tools look up your team ID when you don't pass one explicitly.

Handy extras

vercel open        # open the current project's dashboard in a browser
vercel init        # scaffold a starter project from an example
vercel git connect # connect a Git repository to the project