Roles and permissions

This page describes the Identity and Access Management (IAM) roles and permissions needed for running Connectivity Tests.

You can grant users or service accounts permissions or predefined roles, or you can create a custom role that uses permissions that you specify.

The IAM permissions use a prefix of networkmanagement.

To get or set IAM policies, or to test IAM permissions with the Network Management API, see Manage access policies.

Roles

This section describes how to use predefined and custom roles when granting permissions for Connectivity Tests.

For an explanation of each permission, see the permissions table.

For more information about project roles and Google Cloud resources, see the following documentation:

• Resource Manager documentation
• Identity and Access Management documentation
• Compute Engine documentation describing access control

Predefined roles

Connectivity Tests has the following predefined roles:

• networkmanagement.admin has permission to perform all operations on a test resource.
• networkmanagement.viewer has permission to list or get a specific test resource.

The following table lists the predefined roles and the permissions that apply to each role.

Role	Permissions
Network Management Admin (roles/networkmanagement.admin) Full access to Network Management resources. Lowest-level resources where you can grant this role: Project	networkmanagement.* networkmanagement.config.get networkmanagement.config.startFreeTrial networkmanagement.config.update networkmanagement.connectivitytests.create networkmanagement.connectivitytests.delete networkmanagement.connectivitytests.get networkmanagement.connectivitytests.getIamPolicy networkmanagement.connectivitytests.list networkmanagement.connectivitytests.rerun networkmanagement.connectivitytests.setIamPolicy networkmanagement.connectivitytests.update networkmanagement.locations.get networkmanagement.locations.list networkmanagement.operations.get networkmanagement.operations.list networkmanagement.topologygraphs.read resourcemanager.organizations.get resourcemanager.projects.get resourcemanager.projects.list
Network Management Viewer (roles/networkmanagement.viewer) Read-only access to Network Management resources. Lowest-level resources where you can grant this role: Project	networkmanagement.config.get networkmanagement.connectivitytests.get networkmanagement.connectivitytests.getIamPolicy networkmanagement.connectivitytests.list networkmanagement.locations.* networkmanagement.locations.get networkmanagement.locations.list networkmanagement.operations.* networkmanagement.operations.get networkmanagement.operations.list networkmanagement.topologygraphs.read resourcemanager.organizations.get resourcemanager.projects.get resourcemanager.projects.list

Custom roles

You can create custom roles by selecting a list of permissions from the permissions table for Connectivity Tests.

For example, you can create a role called reachabilityUsers, and grant the list, get, and rerun permissions to this role. A user with this role can rerun existing Connectivity Tests and view updated test results based on the latest network configuration.

Project roles

You can use project roles to set permissions to Google Cloud resources. Because Connectivity Tests must have read access to the Google Cloud resource configurations in your Virtual Private Cloud (VPC) network to run a test, you must grant at least the Compute Network Viewer role (roles/compute.networkViewer) to users or service accounts running a test against those resources. You can also create a custom role or temporarily authorize permissions associated with the preceding role for a specific user.

Alternatively, you can grant a user or service account one of the following predefined roles for Google Cloud projects:

• project.viewer has all the permissions of a networkmanagement.viewer role.
• project.editor or project.owner has all the permissions of the networkmanagement.admin role.

Permissions

This section describes permissions for Connectivity Tests and how to use them when testing different types of network configurations.

Connectivity Tests permissions

Connectivity Tests has the following IAM permissions.

Permission	Description
networkmanagement.connectivitytests.list	Lists all tests configured in the specified project.
networkmanagement.connectivitytests.get	Gets the details of a specific test.
networkmanagement.connectivitytests.create	Creates a new test object in the specified project with the data that you specify for the test. This permission includes permission to update, rerun, or delete tests.
networkmanagement.connectivitytests.update	Updates one or more fields in an existing test.
networkmanagement.connectivitytests.delete	Deletes the specified test.
networkmanagement.connectivitytests.rerun	Reruns a one-time reachability verification for a specified test.

If you don't have permission to create or update a test, the corresponding buttons are inactive. These include the Create connectivity test button and, on the Connectivity test details page, the Edit button. In each case, when you hover over the inactive button, Connectivity Tests displays a message describing the permission that you need.

Permissions for viewing test results

If you don't have permission to view the Compute Engine resources in the network path that you are testing, you can still see the overall test result, but details about the tested resources are hidden.

Note: In the Google Cloud console, the color of the card for each tested resource reflects the test condition of the resource, not the permissions that you have to view the resource.

Project resources

In general, if you don't have access to a project resource listed in a trace, the analysis result shows a message reading in part No permission to view the resource. Connectivity Tests hides the resource type, the resource name, and other details. However, the trace identifies the project that the resource is associated with.

Hierarchical firewall policies

Your trace might include a hierarchical firewall policy that you don't have permission to view. However, even if you don't have permission to view the policy details, you can still see the policy rules that apply to your VPC network. For details, see Effective firewall rules in the hierarchical firewall policies overview.

Permissions across multiple projects

If the network configuration that you test uses VPC Network Peering or Shared VPC, Connectivity Tests must have sufficient permissions to access configurations in the multiple projects that these networks use.

These permissions enable Connectivity Tests to run one or more full traces of the packet path across different networks and projects. Otherwise, Connectivity Tests can access configurations within only that project.

Permissions for Shared VPC networks

To run a test from a service project in a Shared VPC network, you must have the Compute Network Viewer role (roles/compute.networkViewer) or the legacy Project Viewer role (roles/viewer) for the host project. This requirement exists because the network's firewall and route configurations network are located in the host project. You must have one of these roles even if the resources that you are testing exist entirely within a single service project.

To run a test from a Shared VPC host project to virtual machine (VM) instances in a service project, you must also have one of these roles (roles/compute.networkViewer or roles/viewer) in the service project. Additionally, when you create the test, you must provide the service project ID. If you don't provide this ID, the Connectivity Test shows an overall reachability result of Unreachable with an unknown IP address message.

Permissions for VPC Network Peering, Cloud VPN, and Cloud Interconnect

If you have a Connectivity Test that examines reachability between projects that are connected through VPC Network Peering, the results that you see vary depending on your permissions.

To see the full results of the analysis, you must have the Compute Network Viewer role (roles/compute.networkViewer) or the legacy Project Viewer role (roles/viewer) in both projects.

If you have one of these roles for the network that contains the source endpoint, but not the network that contains the destination, the analysis shows a partial result. That is, the analysis shows that the packet was sent to a VPC Network Peering network. However, Connectivity Tests can't provide any additional information for that network.

What's next

• Manage access policies
• Learn about Connectivity Tests
• Create and run Connectivity Tests
• Troubleshoot Connectivity Tests