Netlify team membership is the set of rules by which Netlify decides who counts as a member of a team and whether that person is billed. Netlify changed these rules in April 2026: the documentation states that for existing credit-based Pro teams, “seat charges for existing members are removed at the start of your next billing cycle” and that new members can be invited at no charge from April 14, 2026.[1] Legacy plans, by contrast, still bill per member.[1] A team can therefore contain a mix of free and billable roles depending on its plan generation, which is why a software asset manager must establish whether a Netlify team is on a credit-based or a Legacy plan before counting seats.
Editions
| Plan | Team members | Team Owners | Git Contributors |
|---|---|---|---|
| Free (credit-based) | Limited to 1 free member | 1 | Unlimited on public repositories[2][3] |
| Personal (credit-based) | 1 member; additional seats cannot be added | 1 | Unlimited on public repositories[1][3] |
| Pro (credit-based) | Unlimited, included | Unlimited | Unlimited on all repositories, included[3][2] |
| Legacy Pro | $19 per member per month | Paid | Billed if active[1][4] |
| Enterprise | Custom | Multiple; Organization Owners | Billed if active on Legacy plans[4] |
The pricing page states that Pro costs “$20 /month for unlimited members, with free & unlimited Git Contributors on all repos”, Personal costs “$9/month for 1 member” and Free is “Limited to 1 free member”.[2] Catalog: Team member seat; Credit Pro seats are free and unlimited; Free and Personal cannot add team members.
Metrics
Team members and roles
Netlify roles are Owner, Developer, Publisher, Internal Builder, Git Contributor, Reviewer and Billing Admin.[5]
| Role | What it can do | Charged on Legacy plans |
|---|---|---|
| Owner (Team Owner) | Accesses the entire team account, adds or removes members, changes settings and plans, deletes projects | Yes[5] |
| Organization Owner | Manages an Enterprise organization with multiple teams; has the Team Owner role in all teams by default | Not stated[5] |
| Developer | Manages deploys and project configuration; can approve Reviewers; formerly called Collaborator | Yes[5] |
| Publisher | Visual Editor role that can publish and schedule content | Not stated in the roles page[5] |
| Internal Builder | Builds with Agent Runners; cannot publish to production or change environment variables | Not stated in the roles page[5] |
| Git Contributor | Triggers builds and deploys from a private Git repository; no access to the Netlify app | Only if active[5][4] |
| Reviewer | Reviews Deploy Previews and branch deploys and gives feedback | No[5][4] |
| Billing Admin | Changes the plan and billing details only | Enterprise feature[5] |
The roles page repeats that on the Credit Pro plan team member seats are unlimited and included starting in the base $20 per month plan.[5] It also marks the Billing Admin role as an Enterprise feature, while the credit-based plan comparison lists the Billing Admin role as available on Pro.[5][3] The Publisher and Internal Builder pages do not state the per-seat treatment on Legacy plans, so the table does not infer it. Every team must have at least one Owner, and Owners cannot remove or demote themselves unless another Owner exists.[5] Catalog: Team member seat; Team Owners are paid members on Legacy plans.
Git Contributors
A Git Contributor is a non-team member who triggers a build or deploy through Netlify from a private Git repository. A Team Owner can add contributors manually per deploy request or automatically by enabling auto-approval in team settings.[5] On the Credit Pro plan, “Git Contributors are included in your plan at no additional cost”; known bots such as Renovate or Claude do not count as Git Contributors.[1][3] On Legacy Pro and Enterprise plans, a Git Contributor added to the team counts toward the member total and is billed, but only if they triggered a deploy during the billing period.[4] Netlify does not track Git Contributors for repositories hosted on Cursor Origin, on any plan.[5] Catalog: Git Contributor; Contributors who deploy are included on Credit Pro; Legacy plans bill only active Git Contributors.
Reviewers
The Reviewer role gives a person a Netlify login to review a team’s projects and share feedback, and the Billing FAQ says “With any plan, you can add unlimited free Reviewer roles to your team”.[1] The pricing page also lists Reviewers as unlimited on Free, Personal and Pro.[2] The roles page, however, states that on a credit-based plan “you must have a Pro plan or higher to invite someone with the Reviewer role”.[5] Because the three pages differ for Free and Personal, the Reviewer entitlement of a non-Pro credit-based team should be confirmed in the product. A Team Owner or Developer must approve pending Reviewers before they collaborate on Deploy Previews.[6] Catalog: Reviewer; Reviewer role is free on every plan; Inviting Reviewers on credit plans requires Pro.
Counting and floors
- Free and Personal. Neither can add team member seats.[1]
- Pro (credit-based). Seats and Git Contributors are unlimited and included. Team Owner count is unlimited.[3]
- Legacy Pro. The Team Owner is billed on the number of active members, the plan’s member limit and usage; Reviewers are not charged.[4] Netlify emails Team Owners as they approach the plan’s member limit.[4]
- Billing mechanics on Legacy plans. Seat fees are charged monthly in advance and prorated by days when a seat is added or removed.[4]
- Enterprise. Where access is restricted to a number of individual users on the Order Form, each user’s credentials cannot be shared by more than one individual, and Netlify “reserves the right to charge Customer for any overuse”.[7]
- Concurrent builds and Preview Servers are team-level quantities, not per-member quantities.[3]
Catalog: Enterprise credentials cannot be shared; overuse is chargeable; Legacy Pro bills $19 per team member.
Virtualization and partitioning
Not applicable. Access can be limited at project level: Owners can choose which projects Developers, Publishers, Internal Builders and Reviewers can access, while Git Contributors, Team Owners and Billing Admins cannot be given granular project access.[5] Project access does not change the seat count.
Cloud and BYOL
No bring-your-own-licence rights apply. Enterprise customers can use SCIM-based directory sync so an identity provider manages team access instead of a Team Owner, and SSO, SCIM and organization management are listed as Enterprise features.[5][2] The pricing page marks several access capabilities, including project-level access control, self-serve team creation, org-level SSO and SCIM, as add-ons on some plans.[2]
Programs
- Netlify Open Source plan. The pricing page FAQ says the plan includes monthly credits, free production deploys and unlimited team members for qualifying projects; the page does not state qualifying criteria.[2]
- April 14, 2026 seat change. Existing credit-based Pro teams are not charged for seats from their next billing cycle.[1]
- Legacy to credit migration. A team that switches to a credit-based plan cannot return to Legacy; see Netlify legacy plans and migration.
Audits and compliance
Netlify’s self-serve agreement requires customers to be responsible for all activity under their account and to keep credentials confidential, and requires the Services to be used only by persons at least 13 years old on a device under the customer’s control.[8] The Enterprise Master Subscription Agreement adds that the customer is responsible for its users’ compliance and Netlify may verify compliance from time to time.[7] No seat audit procedure is described in either agreement. For SAM purposes, the practical evidence sources are the team Members page, which lists active and inactive Git Contributors on credit plans, and the Usage & billing page.[5][1]
Out of scope
- Visual Editor editorial permissions and Netlify Database access control details.
- Enterprise organization management and SCIM provisioning procedures.
- Negotiated seat limits on Enterprise Order Forms.