When activating a Looker Studio Pro subscription, you might encounter an error message that says Project is a valid Google Cloud project and you have the permissions. This error can occur for several reasons, including incorrect project configuration or insufficient permissions.
This document describes several potential causes for this error and provides steps to troubleshoot them.
Decision tree
Use the following decision tree to troubleshoot potential causes and solutions for this error:
Troubleshooting steps
The following sections describe the scenarios in the tree in further detail.
Missing IAM permissions
To activate a Looker Studio Pro subscription for a Google Cloud project, you must have the correct IAM permissions on that project.
How to troubleshoot:
Ensure that you have one of the following roles for the project that you are associating with Looker Studio Pro:
- Owner (
roles/owner) - Looker Studio Pro Manager (
roles/lookerstudio.proManager)
These roles include the lookerstudio.pro.manage permission, which is required to manage Looker Studio Pro subscriptions, and the resourcemanager.projects.updateLiens permission, which lets Looker Studio Pro protect your project assets if you cancel your subscription.
For more information about adding permissions, see Grant or revoke a single role.
Overriding IAM deny policy
Even if you have the Owner or Looker Studio Pro Manager role, an IAM deny policy at the organization, folder, or project level might be blocking you from activating Looker Studio Pro. Deny policies override allow policies (like those granted by IAM roles). If a deny policy exists that blocks the lookerstudio.pro.manage permission, you won't be able to complete the activation.
How to troubleshoot:
If you have Organization Administrator permissions, or if you have the Deny Reviewer (roles/iam.denyReviewer) or Deny Admin (roles/iam.denyAdmin) role, you can check for deny policies that might be affecting your project.
You can use Policy Troubleshooter to check why access might be denied:
- In the Google Cloud console, go to the Policy Troubleshooter page.
- For Principal, enter your email address.
- For Resource, enter the project ID.
- For Permission, enter
lookerstudio.pro.manage. - Click Check Access.
If Policy Troubleshooter indicates that access is denied, it will provide information about the policy that is causing the denial. For more information about managing deny policies, see Deny access to resources.
Project not linked to an active billing account
A Looker Studio Pro subscription must be linked to a Google Cloud project that has an active Cloud Billing account.
How to troubleshoot:
Ensure that the project you're using for Looker Studio Pro is linked to an active billing account. For more information, see Enable billing for an existing project.
User and project are in different organizations
If you're trying to activate Looker Studio Pro using a Google Cloud project that belongs to a different organization than your user account, you might encounter this error.
How to troubleshoot:
Ensure that your user account and the Google Cloud project are in the same organization.
Incorrect user account type
Looker Studio Pro subscriptions must be associated with a Google Workspace or Cloud Identity organization. You can't sign up for Looker Studio Pro with a personal Google Account (such as an @gmail.com account).
How to troubleshoot:
Make sure that you are signed in with your managed Google Workspace or Cloud Identity account before you try to activate Looker Studio Pro.
Project already has a Looker Studio Pro subscription
Each Google Cloud project can be associated with only one Looker Studio Pro subscription.
How to troubleshoot:
If the project you selected is already linked to a Looker Studio Pro subscription, you must select a different project.