Solving orphaned GCP project access issues

Google Workspace Developers Q&A
1

Continuing the discussion from Orphaned Google Cloud Project Blocking Producer Portal Access – Needs Org Reassignment:

This happens because the project is not attached to any organization (“No Organization”), and you don’t have the required IAM permissions (resourcemanager.projects.getIamPolicy) on that project. Even if you are a Super Admin in your org, org-level roles do not apply to projects outside the org.

Identify who created the project (billing account, logs, emails).Ask them to:

Grant you Project Owner role or move the project to your organization.

There is no self-service way to fix this from your side due to permission boundaries.This requires Google internal intervention or existing project owner access.

2

Hi Sujai,

Thanks for the explanation. I understand why org-level Super Admin roles don’t apply to a project in “No Organization.”

In this case, the project (thematic-axon-1tvcb) was auto-created by Google as part of the Producer Portal workflow. I don’t have an internal owner to request access from, so there’s no way for me to self-assign permissions or move it.

This is currently blocking all Producer Portal access and Marketplace operations, including active deals. The only way forward is for Google to either:

  1. Grant me Project Owner/IAM access, or

  2. Re-parent the project to our organization (URL Removed by Staff).

I’m looking for guidance on the correct escalation path to get internal intervention. Any advice from the community on how to route this to the appropriate Google internal team would be greatly appreciated.

1 Like