GCP permissions
Permissions North.cloud requires from your GCP account.
GCP IAM Permissions & Deployment
North requires carefully scoped GCP permissions so our application can access billing and usage data required by our ML engine to provide automated FinOps recommendations. We purposefully limit all permissions to the minimum necessary for your financial analysis and do not request access to your workloads or sensitive application data.
GCP uses Workload Identity Federation and BigQuery dataset sharing to provide secure, fine-grained access to only your billing data—no North service account keys required.
What North CAN NOT do
Read sensitive data from your workloads or databases
View or edit network rules and security groups
Create, modify, stop, or terminate any compute instances or other machines
Change, copy, or export any development, test, or production data
Access any data outside of the billing dataset you explicitly share, and the utilization metrics you grant for Rightsize
Modify your GCP resources or configurations
The following sections explain the IAM permissions required and why each permission group is needed.
Permission Groups Explained
1. Baseline (Default) – Read-Only Billing Data via BigQuery
Purpose: These permissions allow North to read GCP billing, usage, and cost details from your BigQuery billing export. These are required for all FinOps analysis and recommendations.
Key Roles Explained:
roles/bigquery.dataViewer(BigQuery Data Viewer): Allows North to read data from tables in your billing dataset. Enables querying cost and usage tables for cost analysis.Read-only: No permission to change, delete, or export data.
No access to data outside the shared dataset.
roles/bigquery.metadataViewer(BigQuery Metadata Viewer): Allows North to view metadata (like table structure and schema) about your billing dataset, and list billing export tables.Read-only: Cannot modify table metadata or datasets.
Cannot see metadata for datasets you do not share.
How Access Works:
North uses GCP Workload Identity Federation to securely assume access to the shared dataset, without requiring service account keys.
To grant North access, you assign both roles above to the workload identity principal provided by North during onboarding. This principal follows a standard, auditable format and ensures that only North’s authorized system can access your shared data.
2. Auto-Purchasing (Optional) – Buying Commitments in Your Own Account
Purpose: The baseline roles above let North read your billing data and recommend commitments. They do not let North buy anything. Autobot needs a separate set of roles before it can purchase commitments directly in your own Google Cloud account.
These roles are optional. Grant them only if you want Autobot to purchase on your behalf. North verifies them separately from the baseline roles, and a missing purchasing role does not affect your account's overall verification status.
Key Roles Explained:
Google Cloud splits committed use discounts across three mechanisms. Each one operates at a different scope, so each role is granted at the scope its mechanism actually works at.
roles/compute.admin
Resource-based CUDs for Compute Engine
Your organization
roles/bigquery.resourceAdmin
BigQuery capacity commitments
Your designated reservation admin project
roles/consumerprocurement.orderAdmin
Spend-based CUDs and Flexible CUDs
Your billing account
North grants these to the same principal the baseline flow already uses. No second principal is created. Only the roles bound to it differ.
Notes on the scopes, because they are not interchangeable:
roles/compute.adminis bound at the organization, not per project. One grant then covers every project under it, including projects you add later. A per-project grant leaves any new project uncovered until onboarding runs again.roles/bigquery.resourceAdminis bound on one project only. Capacity commitments live on the single admin project you designate for reservations. Confirm that the project you name really is that admin project. Do not grant this role at the organization level, because that would give every project in the organization reservation-admin rights it does not need.roles/consumerprocurement.orderAdminis bound on the billing account. Consumer Procurement orders are billing-account-scoped, so there is no organization-level equivalent. One grant covers every project linked to that billing account. North asks for this role rather thanroles/billing.admin, which is a much broader grant this feature does not need.
3. Rightsize (Optional) - Reading Utilization Metrics
Purpose: Rightsize reads utilization metrics from Cloud Monitoring to size your Compute Engine instances. Without this role, North still lists your resources, but Rightsize cannot size them. Everything else in North keeps working.
Key Role Explained:
roles/monitoring.viewer(Monitoring Viewer): Allows North to read utilization metrics from Cloud Monitoring.Read-only: Limited to utilization metrics.
How Access Works:
Grant the role on your billing project to the same principal that reads your billing export. No second principal is created. Then add every project you want Rightsize to analyze to your billing project's metric scope. A project outside the metric scope is not analyzed. For the steps, see Compute Engine.
Security Model
Workload Identity Federation:
No service account keys required. Credentials are time-limited, rotated, and cannot be reused.
North can only access the specific dataset you share, and the utilization metrics you grant, and only with roles you choose.
Access is logged in GCP Cloud Audit Logs, providing full traceability.
The principal includes an attribute (
attribute.aws_role/NorthGCPReadOnlyRole) to ensure only North’s authorized systems can assume the role.
Data Isolation:
North only has access to the billing dataset you explicitly share, and to utilization metrics if you grant Monitoring Viewer
Access is always read-only—North cannot modify or delete your data
North cannot access any other datasets or resources
Last updated
Was this helpful?

