Summary and recommendation
Vercel user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Vercel organizes team access through four fixed team-level roles - Owner, Member, Viewer, and Billing - plus a project-scoped Developer role available only on Enterprise. There are no custom roles; permissions are tied to the predefined set. Project-level access controls, which let you restrict individual members to specific projects, are gated behind Enterprise.
On Pro, every member sees every app in the team by default, with no way to limit project visibility. Admins manage the full member lifecycle from Team Settings → Members at vercel.com/teams/[team-slug]/settings/members.
Quick facts
| Admin console path | Team Settings → Members |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Enterprise (or Pro with add-on) |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Owner | Full administrative control: billing, team settings, member management, all projects, delete team. Only role that can manage billing and delete the team. | Nothing restricted; has all permissions. | Pro or Enterprise (Hobby is single-user only) | $20/user/month on Pro; custom on Enterprise | There must always be at least one Owner. Transferring ownership requires the recipient to already be a team member. |
| Member | Can create and deploy projects, view all team projects, manage their own projects, and invite other members (on Pro/Enterprise). | Cannot access billing, cannot change team settings, cannot remove other members, cannot change team roles. | Pro or Enterprise | $20/user/month on Pro; custom on Enterprise | Members can see all projects in the team by default unless project-level access controls are configured (Enterprise only). |
| Viewer | Read-only access to projects and deployments. Can view logs and deployment details. | Cannot deploy, cannot modify project settings, cannot manage team members. | Pro or Enterprise | $20/user/month on Pro; custom on Enterprise | Viewer seats cost the same as Member seats; there is no reduced-cost viewer tier. |
| Billing | Can view and manage billing information, invoices, and payment methods. | Cannot deploy projects, cannot manage team members, cannot change project settings. | Pro or Enterprise | $20/user/month on Pro; custom on Enterprise | Billing role is separate from Owner; useful for finance team members who should not have technical access. |
| Developer (Project-level role) | On Enterprise, can be scoped to specific projects with deploy and settings access for those projects only. | Cannot access projects they are not explicitly added to (Enterprise project-level access control). | Enterprise | Custom (Enterprise pricing) | Project-level access controls are an Enterprise-only feature; on Pro, all Members see all projects. |
Permission model
- Model type: role-based
- Description: Vercel uses predefined team-level roles (Owner, Member, Viewer, Billing). On Enterprise, project-level access controls allow restricting individual members to specific projects. There are no fully custom roles; permissions are tied to the fixed role set.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Team-level roles apply globally across all projects on Pro. Enterprise adds project-scoped access, allowing per-project role assignment. No field-level or action-level custom permission sets are available.
How to add users
- Navigate to vercel.com/teams/[team-slug]/settings/members.
- Click 'Invite Members'.
- Enter the invitee's email address.
- Select the role to assign (Owner, Member, Viewer, or Billing).
- Click 'Send Invite'.
- Invitee receives an email and must accept the invitation to join the team.
- On Enterprise with SCIM enabled, users can also be provisioned automatically via the connected IdP without a manual invite.
Required fields: Email address, Role selection
Watch out for:
- Invitees must have or create a Vercel account to accept the invitation.
- Pending invitations count toward the seat limit and billing on Pro.
- On Hobby plan, teams are not supported; only a single personal account exists.
- If SAML SSO is enforced, new members must authenticate via SSO before accessing the team.
- Invitations expire after 24 hours if not accepted.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise (native SCIM); Pro with Directory Sync add-on ($150/month) |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Vercel does not have a 'deactivate' state for team members. Removing a member is a hard removal from the team. The user's Vercel account itself is not deleted; they simply lose access to the team. With SCIM, deprovisioning in the IdP removes the user from the team automatically.
- Navigate to vercel.com/teams/[team-slug]/settings/members.
- Locate the member to remove.
- Click the '...' (overflow) menu next to the member's name.
- Select 'Remove Member'.
- Confirm the removal in the dialog.
- The member immediately loses access to the team and its projects.
| Data impact | Behavior |
|---|---|
| Owned records | Projects created by the removed member remain in the team and are not deleted. Deployments and project history are preserved. |
| Shared content | All team projects, deployments, and environment variables remain intact and accessible to remaining team members. |
| Integrations | Integrations connected under the removed member's personal OAuth tokens may break if those tokens are revoked. Team-level integrations are unaffected. |
| License freed | The seat is freed immediately upon removal, and billing adjusts at the next billing cycle on Pro. |
Watch out for:
- You cannot remove the last Owner of a team; another member must be promoted to Owner first.
- If the removed user was the sole manager of a third-party integration connected via their personal account, that integration may stop functioning.
- Removal is immediate and irreversible from the UI; the user must be re-invited to regain access.
- With SCIM, removing a user from the IdP group automatically removes them from the Vercel team; manual removal in Vercel is not required when SCIM is active.
- Pending (unaccepted) invitations must be cancelled separately; they do not auto-cancel when a member is removed.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Pro Seat | All roles (Owner, Member, Viewer, Billing) on the Pro plan. No differentiated pricing by role. | $20/user/month |
| Enterprise Seat | All roles including project-scoped access controls, SSO, SCIM, advanced security features. | Custom (negotiated; reported minimum ~$20–25K/year for the team) |
- Where to check usage: Team Settings → Billing (vercel.com/teams/[team-slug]/settings/billing) shows current member count and seat charges.
- How to identify unused seats: No built-in 'last login' or activity report is available in the Vercel dashboard for identifying inactive members. Admins must manually review the Members list and cross-reference with deployment activity or use IdP-side reporting when SCIM is active.
- Billing notes: On Pro, all seats (including pending invitations) are billed at $20/user/month. Seats are freed at the next billing cycle after removal, not immediately prorated in all cases. SSO add-on is $300/month; Directory Sync (SCIM) add-on is $150/month on Pro. Enterprise bundles SSO and SCIM. Hobby plan does not support teams.
The cost of manual management
Vercel offers no built-in last-login or activity report, so identifying unused seats requires manually cross-referencing the Members list against deployment history - or relying on IdP-side reporting when SCIM is active. Viewer seats carry the same per-seat cost as full Member seats, so there is no cost relief for read-only users.
On Pro, pending invitations count toward the seat limit and billing at $20/user/month. Invitations expire after 24 hours, creating re-work when recipients are slow to respond. Seat charges free up at the next billing cycle after removal, not immediately.
What IT admins are saying
The most consistent friction reported by Vercel teams centers on add-on pricing and access control gaps. On Pro, SSO and SCIM are available as paid add-ons ($300/month and $150/month respectively), which stack on top of per-seat costs and add up quickly for mid-size teams.
The absence of project-level visibility controls on Pro is a recurring complaint: every app is visible to every Member, with no workaround short of upgrading to Enterprise.
The 24-hour invitation expiry and the lack of any inactive-user reporting are also frequently cited as operational friction points.
Common complaints:
- Add-on pricing on Pro adds up quickly ($300/month SSO + $150/month SCIM = $450/month on top of per-seat costs).
- No reduced-cost viewer or read-only seat tier; Viewer seats cost the same as full Member seats.
- No built-in inactive user or last-login reporting makes it difficult to audit unused seats.
- Project-level access controls (restricting members to specific projects) are Enterprise-only; Pro teams have no way to limit project visibility.
- Invitation expiry (24 hours) is short and causes friction when inviting users who are slow to respond.
- Enterprise pricing is not publicly listed; requires contacting sales.
- Permission changes take effect immediately with no staging or review step, which can cause accidental lockouts.
- Removing a member who owns OAuth-connected integrations can silently break those integrations.
The decision
Stay on manual provisioning if your team is small, turnover is low, and you are on Pro without the SCIM add-on - the invite flow from Team Settings → Members is straightforward for occasional changes.
Move to SCIM-backed provisioning if you need reliable, auditable lifecycle management at scale, or if your compliance posture requires automated deprovisioning.
If project-level access control is a hard requirement - restricting members to only the projects they need - Enterprise is the only path. Pro offers no equivalent, regardless of how roles are configured.
Bottom line
Vercel's manual access model is workable for small, stable teams but shows strain as headcount grows: no inactive-user reporting, no reduced-cost viewer tier, and no project-scoping on Pro mean that governance overhead scales with team size.
The add-on pricing for SSO and SCIM on Pro is a real cost consideration before committing to that plan tier.
Teams with strict access control or audit requirements will find the Enterprise tier - with bundled SSO, SCIM, and project-level controls - the more defensible long-term choice.
Automate Vercel workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
