Notification

This Help Center is moving to Cloud. Learn more about the migration.

Consolidate multiple Looker Studio Pro subscriptions

How to merge Looker Studio content and subscriptions into a single Cloud project.
This article is intended for Cloud Identity and Workspace administrators who want to centralize management of Looker Studio Pro under a single Google Cloud project. 

For example, say that several departments in your organization have subscribed to Looker Studio Pro, and each department manages its content within their own Cloud projects. Managing Looker Studio Pro with a single subscription and a single project can make it easier to manage billing and access controls.

To consolidate multiple subscriptions and projects, follow these steps: 

  • Prevent users from creating new Looker Studio Pro departmental subscriptions 
  • Find Looker Studio Pro projects in your organization
  • Choose a single Looker Studio Pro project to use
  • Add users and licenses to the chosen Looker Studio Pro project
  • Move existing content into the chosen Looker Studio Pro project
  • Make the chosen project the default project
  • Remove users and licenses from other projects

Prevent users from creating new Looker Studio Pro departmental subscriptions 

You can prevent users from creating Pro subscriptions by using an IAM deny policy. To set up a deny policy, complete the following tasks:

  1. Select or create a Google Group that contains the users who will manage Looker Studio Pro. For example: [email protected].
  2. Create a deny policy that denies the datastudio.googleapis.com/pro.manage permission to everyone except the example Google Group. Following is an example deny policy that uses the [email protected] Google Group:

{

  "deniedPrincipals": [

    "principalSet://goog/public:all"

  ],

  "exceptionPrincipals": [

    "principalSet://goog/group/[email protected]"

  ],

  "deniedPermissions": [

    "datastudio.googleapis.com/pro.manage"

  ]

}

  1. Attach the deny policy to your organization.

Learn how to set up an IAM deny policy for your organization.

Find Looker Studio Pro projects in your organization

To locate the Cloud projects that are in use for Looker Studio Pro, follow these steps in the Looker Studio Pro user interface:

  1. Grant yourself an organization-level IAM role, such as the lookerstudio.proManager role, that includes the lookerstudio.pro.manage permission. 
  2. Sign in to Looker Studio Pro.
  3. To view the list of Pro subscriptions in your organization, in the left navigation, click Pro Subscriptions.

Choose a single Looker Studio Pro project to use

Choose one of the existing Looker Studio Pro projects to use as the single project for your organization. You might choose the project with the most content or the one with the most licenses. Alternatively, you might create a new project to be the chosen Looker Studio Pro project.

Add users and licenses to the chosen Looker Studio Pro project

Use the Looker Studio Pro user interface or the Google Cloud console to add your existing users and licenses to the chosen Looker Studio Pro project. You'll need to repeat this process for each subscription in your organization if you want to maintain those licenses.

Learn more about managing Looker Studio Pro subscriptions.

Move existing content into the chosen Looker Studio Pro project

To consolidate existing content from the original projects, move that content into the chosen project using the Looker Studio UI. See add and remove team workspace assets for more information.

Make the chosen project the default project

Setting a default Looker Studio Pro project ensures that users can only create content in an organization-managed location. Follow the directions in Set a default Looker Studio Pro project and select your chosen Looker Studio Pro project to be the default project.

Remove users and licenses from other projects

Finally, remove the users and licenses from the original Looker Studio Pro projects. 

Important

Don't skip this step: if an individual user belongs to multiple subscriptions, you will be charged for a license for each subscription that user is in.

Additionally, unless your organization sets up a deny policy as described previously, users will still be able to create new Pro subscriptions and create Pro content in any project that they have a license on.

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Google apps
Main menu
10917063296751861404
true
Search Help Center
true
true
true
true
true
102097
false
false