Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit f3e3c74

Browse files
Update gcp-connect.rst
Fix
1 parent c6931dd commit f3e3c74

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

gdi/get-data-in/connect/gcp/gcp-connect.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,9 +101,9 @@ Your GCP integration is now complete.
101101
Using a single principal for your resources
102102
++++++++++++++++++++++++++++++++++++++++++++++++
103103

104-
In IAM you can grant access to your resources to one or more entities called principals. The principal provided for the project needs either the ``serviceusage.services.use`` permission or the Service Usage Consumer role.
104+
In IAM you can grant access to your resources to one or more entities called principals, regardless of the authentication method (single Service Account or Workload Identity Federation).
105105

106-
Regardless of the authentication method (single Service Account or Workload Identity Federation), if you're using a single principal for multiple projects, GCP tracks all API usage quota in the project where the principal originates from. This can result in throttling in your integration. To mitigate this, select :strong:`Use quota from the project where metrics are stored`.
106+
If you're using a single principal for multiple projects, GCP tracks all API usage quota in the project where the principal originates from, which can result in throttling in your integration. To mitigate this, select :strong:`Use quota from the project where metrics are stored`. To use this option the principal provided for the project needs either the ``serviceusage.services.use`` permission or the Service Usage Consumer role.
107107

108108
For a more detailed description see :new-page:`Principals <https://cloud.google.com/iam/docs/overview#concepts_related_identity>` in GCP's docs.
109109

0 commit comments

Comments
 (0)