Stay organized with collections Save and categorize content based on your preferences.
Access control with IAM
Service Usage usesIdentity and Access Management (IAM) tocontrol access to services. This page explains the IAM roles andpermissions related to Service Usage and how to use them to controlaccess.
Resource model
For Service Usage, there are three relevant resources:
The service you are using.
The project from which you are using the service.
The operation or long-running operation returned by certain methods.
Each Service Usage method requires a permission on one or more of theseresources.
IAM permissions
The following table shows the required permissions for eachService Usage API method. You can also find this information in theAPI reference.
On the project:serviceusage.quota.update On the service:servicemanagement.services.bind
To use a project for quota and billing purposes. For more information, seeSystem parameters.
On the project:serviceusage.services.use
IAM roles
With IAM, you give users permission by granting them a role. Thefollowing tables list IAM basic and predefined roles, and thepermissions related to Service Usage that those roles include.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-02-19 UTC."],[],[]]
