We’ve updated how you manage who can access what on your Netlify project and created a new role designed for the workflow needs of cross-functional AI-assisted builders.

Teams have asked for clearer ways to support people building internal tools and people collaborating on existing projects with AI agents and some guardrails.

With the new Internal Builder role and more granular project access control, Netlify now better supports new ways of working with AI across your cross-functional teams.

Introducing the Internal Builder role

This role is ideal for marketers building campaign pages, HR teams spinning up internal sites, or anyone using AI tools to ship without a traditional dev workflow.

The Internal Builder role is built to cover these two use cases:

• Build with Agent Runners with guardrails for existing projects
• Support internal tool builders with their new projects

Build with Agent Runners with guardrails

Internal Builders can use Agent Runners to build and iterate on web projects with guardrails that support the ways cross-functional teams work.

The Internal Builder role can iterate on existing web projects using Agent Runners but cannot publish directly to production or access Project configuration settings, such as to change environment variables. This ensures the Internal Builder doesn’t accidentally break existing functionality.

For projects connected to a Git provider, the Internal Builder can open a pull request for review from their agent run. This allows Developers and Owners to decide when to go live with changes.

Use cases supported:

• Marketing team member who needs to build campaign landing pages quickly with stakeholder review
• Designer who iterates on pricing page with AI assistance with stakeholder review

Support internal tool builders

Once someone with an Internal Builder role creates a project, they automatically get a Developer role on that project without changing their role and access permissions to other projects.

This allows your cross-functional teams to own the building process for their internal tools.

Use cases supported:

• HR team member who wants to build an information site for a company trip to Mexico
• Sales rep building internal tools for their team

New granular project access

We’ve upgraded the ways you can manage project access for your team members.

Team Owners can specify project access when adding team members to projects or when they edit existing project access.

They can assign a role scoped only to specific projects or to all projects (including future ones).

This means the same person can be an Internal Builder on most projects but a Developer on the internal tool they’ve created. Access can be scoped to exactly what each person needs.

For more details, check out our docs on Roles and permissions and Manage project access.

Try it out

To add an Internal Builder to your team, go to your team’s Members page and invite a new member or update an existing member’s role. Let us know if you have any feedback.