Skip to main content
Question

Unable to remove orphaned demo project listing round-chemist-rjp1j due to missing IAM permissions

  • August 2, 2026
  • 1 reply
  • 12 views

mayankitaliya

Hi Community,

I am seeing round-chemist-rjp1j (and fir-demo-project) listed under my resources, but I do not own this project. When attempting to access or view settings, I get the error:

resourcemanager.projects.getIamPolicy (missing)

Since I am not an owner, I am unable to file technical support cases or delete the project. Could a Google representative or community manager help disassociate or clear this project listing from my account ( [removed by moderator] )?

Thanks!

1 reply

thineth_dasun
Forum|alt.badge.img+5

Hi ​@mayankitaliya ,

This is actually a very common scenario when working with Google Cloud / Firebase, and there is no need to worry!

Here is what is happening and how you can resolve/clean this up:

Why do these projects appear?

  1. fir-demo-project: This is a default/sample project created automatically by Google Firebase when testing Firebase demos, tutorials, or codelabs.

  2. round-chemist-rjp1j: Projects with auto-generated names like this are usually created during Google Cloud / Qwiklabs / Firebase interactive labs or third-party integrations (like Google Colab, App Engine starter templates, etc.) where you authorized an application or sample project in the past.

Why do you get resourcemanager.projects.getIamPolicy missing?

When these temporary or demo environments expire, your IAM access to the underlying project is revoked or the project is shut down by the primary system, leaving a residual cached entry in your GCP Console project selector dropdown.

How to remove or hide them from your Console:

  1. Recent Projects List (Console UI):

    • Click on the Project Selector dropdown at the top bar of the Google Cloud Console.

    • Go to the Recent tab.

    • Click the Three Dots (⋮) next to the project name and select Remove from list.

  2. Clear Browser Cache / Cookies: Sometimes the Google Cloud Console caches project resource IDs locally in your browser. Clearing site data for console.cloud.google.com will clean up stale entries.

  3. IAM Permissions: If you were added as a external user or viewer in a shared organization, you can visit the IAM & Admin > IAM page (if accessible) and remove your account from the project roles.

Note: Google Community Managers cannot directly edit or remove backend project links from user accounts for privacy and security reasons, but removing them from your local project list/cache will resolve the view issue.

Hope this helps clear up the mystery!