Google Cloud Networking IAM Roles: Network Admin, Security Admin, Network User and Shared VPC Admin

GCP Study Hub
November 11, 2026

Google Cloud's predefined Compute Engine networking roles are built around a split of duties. One role manages connectivity resources, another manages firewall rules and SSL certificates, and a third only lets people use networks that already exist. Shared VPC adds its own administrative roles on top of those. Least-privilege scenarios on the Professional Cloud Network Engineer exam test which role does what, so the boundaries between the roles are more useful to learn than their full permission lists.

Compute Network Admin

Compute Network Admin (roles/compute.networkAdmin) creates, modifies and deletes networking resources such as VPC networks, subnets, routes, Cloud Routers, VPN tunnels and VLAN attachments. Google documents it as the role for people who create, modify and delete VLAN attachments, and it includes the Cloud Router permissions that go with them, which matters because every attachment is paired with a router.

The role deliberately excludes write access to firewall rules and SSL certificates, but it gives read-only access to them. A connectivity team that holds Network Admin can view firewall rules while troubleshooting without being able to change them. The role is scoped to networking, so it doesn't let its holders manage VMs, storage buckets or other unrelated services. It also lacks the permission to enable a Shared VPC host project.

Compute Security Admin

Compute Security Admin (roles/compute.securityAdmin) is the counterpart meant for the security team. It grants full control over firewall rules and SSL certificates, including creating and changing VPC firewall rules and turning on Firewall Rules Logging for a rule.

In a Shared VPC, the firewall rules belong to the host project, so Compute Security Admin is granted on the host project, not on a service project. A grant in the wrong project gives no access to the rules that matter.

Compute Network User

Compute Network User (roles/compute.networkUser) only lets members use existing networks and subnets, such as attaching resources to a Shared VPC subnet when they create resources in a service project. It has no firewall permissions at all, and it can't create or manage subnets, routers or tunnels. It can be granted on individual subnets, or at the host project level, where it lets developers use every current and future subnet in that project.

Firewall policy and logging roles

  • Compute Organization Security Policy Admin (roles/compute.orgSecurityPolicyAdmin) manages hierarchical firewall policies at the organization or folder level. It doesn't grant permission to create VPC firewall rules inside a project.
  • Logs Viewer (roles/logging.viewer) reads log entries in Cloud Logging, which is where firewall rules logs are written.
  • Logs Bucket Writer (roles/logging.bucketWriter) only writes entries into a log bucket. It doesn't let anyone read firewall rules logs.

Basic roles and custom roles

The basic Editor role lets a user change nearly every resource in a project, and Organization Administrator controls IAM for the whole organization. Both go far beyond least privilege for networking work.

When policy prefers predefined roles, a custom role is the wrong choice whenever a predefined role fits. A custom role also has to include every permission the job needs across the whole lifecycle of the resources involved, and networking jobs tend to span related resources, such as the Cloud Router that goes with each VLAN attachment. A hand-built list of permissions can easily leave something out, while Compute Network Admin already includes the Cloud Router permissions that go with attachments.

Shared VPC Admin: two roles together

Google's Shared VPC documentation describes a Shared VPC Admin as someone who holds two roles:

  • Compute Shared VPC Admin lets the person enable host projects and attach service projects. On its own it can set IAM policy on individual subnets, but it can't change a host project's IAM policy.
  • Project IAM Admin lets the person change the IAM policy of each host project. That is needed to grant Compute Network User at the project level so developers can use every current and future subnet.

Where the pair is bound matters. The aim is to cover every host project with the fewest bindings, which can mean granting both roles once at a higher level of the resource hierarchy rather than repeating the same two grants in many places.

The pair is also broad. Held on a folder, it lets someone enable host projects, attach service projects and delegate access across many projects, so it is far more access than a narrow networking task needs.

Service agents in a Shared VPC

People aren't the only principals that need host project roles. When GKE creates clusters on shared subnets, the service project's GKE service agent builds the cluster, but the subnets and firewall rules it works with belong to the host project. Its roles are therefore granted in the host project:

  • Kubernetes Engine Host Service Agent User lets the agent use the host project's GKE resources.
  • Compute Network User lets it place nodes and load balancers on the shared subnets.
  • Compute Security Admin is needed if GKE should manage its own firewall rules in the shared network.

The service project's Google APIs service account also needs Compute Network User on the shared subnets. Granting any of these roles in the service project instead doesn't help, because access to shared subnets and firewall rules is checked in the host project.

Choosing the narrowest role

For the Professional Cloud Network Engineer exam, least-privilege decisions come down to two steps. First, match the task to the narrowest predefined role: Network Admin for connectivity resources, Security Admin for firewall rules and SSL certificates, Network User for using existing subnets, and the Shared VPC Admin pair for enabling host projects and attaching service projects. Second, grant it on the resource that owns what the task touches, which in a Shared VPC is usually the host project.

Our Professional Cloud Network Engineer practice exams cover networking IAM roles alongside Shared VPC and Cloud NGFW firewall rules, with detailed explanations that drill these distinctions.

Get tips and updates from GCP Study Hub

arrow