在 Looker 数据洞察中，个人用户拥有自己创建或转移给他们的资源（报告、数据源和探索）。如需在所有者离开组织后让 Looker Studio 资源正常运行，管理员必须将这些资源转移给其他用户。否则，这些资源可能会被删除，并且系统会撤消离职用户的数据凭据，从而破坏该用户的报告和数据源。
另一方面，Looker Studio Pro 素材资源采用分层结构，您的 Cloud Identity 或 Google Workspace 组织是最终所有者。借助组织所有权，即使个人所有者离开组织，您的 Looker Studio 资源也能继续正常运行。
具体而言，组织所有权具有以下优势：
用户创建的所有 Looker Studio 素材资源都存储在您控制和管理的 Google Cloud 项目中。
如果 Looker Studio Pro 素材资源的创作者离开贵组织，这些素材资源将受到保护，不会被删除。
您可以使用 IAM 分配适用于贵组织中所有 Looker Studio Pro 素材资源的项目级权限。
Looker Studio Pro 素材资源可供其他 Cloud 服务使用（例如 Dataplex 中的谱系）。
在贵组织中使用 Looker Studio Pro
如需在贵组织中使用 Looker Studio Pro，您需要将 Looker Studio Pro 与 Google Cloud 项目相关联。您还可以选择为项目添加主账号，以管理 Looker Studio 资产。
关联到 Google Cloud 项目
若要完成此步骤，您需要提供一个 Google Cloud 项目，用于管理 Looker Studio 素材资源。此项目还将用于向贵组织收取 Looker Studio Pro 订阅费用。
Cloud 项目要求
您选择的项目必须使用贵组织用于 Looker Studio 订阅的结算账号。
当您设置 Looker Studio Pro 资源的组织所有权时， Google Cloud 系统会自动在项目上创建安全锁，以防止意外删除这些资源。确保您拥有 resourcemanager.projects.updateLiens 权限（由 roles/owner 和 roles/resourcemanager.lienModifier 角色授予），以便 Google Cloud 为您创建质押权。
执行升级到 Looker Studio Pro 的用户必须拥有 Workspace Services Admin 角色，或拥有在项目所属组织中获得 Manage Looker Studio Settings 特权的其他角色。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[],[],null,["# Link a Looker Studio Pro monthly active user subscription to a Google Cloud project\n\n| **Intended audience** : This document is intended for Cloud Identity or Google Workspace administrators whose organization has a Looker Studio Pro subscription that was set up for them by Google Sales or a Google reseller partner with Monthly Active User pricing. If your organization is not already using Looker Studio Pro, or if your subscription was set up using the self-service, division-based pricing model, this document doesn't apply to you. [Learn more about the Looker Studio Pro self-service upgrade process](/looker/docs/studio/upgrade-looker-studio-content-to-looker-studio-pro).\n\nIn Looker Studio, individual users own the assets (reports, data sources, and explorations) that they create or that have been transferred to them. To keep Looker Studio assets working after their owner leaves an organization, an administrator must transfer those assets to another user. Otherwise, those assets will likely be deleted and the departing user's data credentials will be revoked, breaking that user's reports and data sources.\n\nLooker Studio Pro assets, on the other hand, are [organized hierarchically](/resource-manager/docs/cloud-platform-resource-hierarchy), with your Cloud Identity or Google Workspace organization as the ultimate owner. Organizational ownership ensures that your Looker Studio assets continue to work even if their individual owner leaves the organization.\n\nSpecifically, organizational ownership offers the following benefits:\n\n- All the Looker Studio assets that your users create are stored in a Google Cloud project that you control and manage.\n- Looker Studio Pro assets are protected from deletion should their creator leave your organization.\n- You can use IAM to assign project-level permissions that apply to all Looker Studio Pro assets in your organization.\n- Looker Studio Pro assets are available to other Cloud services (for example, lineage in Dataplex).\n\nUse Looker Studio Pro in your organization\n------------------------------------------\n\nTo use Looker Studio Pro in your organization, you'll need to link Looker Studio Pro to a Google Cloud project. Optionally, you can add principals on the project to manage Looker Studio assets.\n\n### Link to a Google Cloud project\n\nTo complete this step, you'll provide a Google Cloud project which you'll use to manage Looker Studio assets. This project will also be used to bill your organization for your Looker Studio Pro subscription.\n\n#### Cloud project requirements\n\n| Choose your Google Cloud project carefully! Once Looker Studio is linked to your project, you can't move your Looker Studio assets to another project. We recommend using a project dedicated to Looker Studio.\n\n- The project that you choose must use the same billing account that your organization uses for your Looker Studio subscription.\n- When you set up organizational ownership of Looker Studio Pro assets, Google Cloud automatically creates a [lien](/resource-manager/docs/project-liens) on the project to prevent accidental deletion of those assets. Be sure you have the `resourcemanager.projects.updateLiens` permission, which is granted by the `roles/owner` and `roles/resourcemanager.lienModifier` roles, so that Google Cloud can create the lien for you.\n- The user who performs the upgrade to Looker Studio Pro must must have the [Workspace Services Admin](https://support.google.com/a/answer/2405986#services_admin) role, or a another role that grants them the `Manage Looker Studio Settings` privilege in the organization that owns the project.\n- The user who performs the upgrade to Looker Studio Pro must also have the [**owner** role](/iam/docs/understanding-roles#owner) for the project.\n\n**For resellers**: The resold customers will need to provide a project that is linked to the billing account of the reseller subscription.\n\nSee the [best practices](#best) section for additional tips before proceeding.\n\n### Steps\n\n1. [Sign in](https://admin.google.com/) with an administrator account to the **Google Admin console**.\n\n | **Note:** If you aren't using an administrator account, you can't access the Admin console.\n2. In the Google Cloud console, go to **Billing** and then select [My Projects](https://console.cloud.google.com/billing/projects).\n\n3. Locate the project that you want to use for Looker Studio asset management and billing and make a note of its project ID.\n\n4. [Sign in to Looker Studio.](https://lookerstudio.google.com)\n\n5. In the left navigation, click **Enterprise Admin**.\n\n6. In the settings dialog that appears, on the left, click **Project ownership**.\n\n7. In the **Project ID** field, enter your Google Cloud project ID.\n\n### Optional: Add principals to the project\n\nIndividual Looker Studio users DO NOT need to be added to the project. However, if you want to allow others in your organization to manage the Looker Studio project, you can add principals to that project using the [IAM resource manager](/resource-manager/docs/access-control-proj) in the Google Cloud console. See the best practices section for advice.\n\nYou can grant principals the following IAM roles:\n\nKeep the following information in mind while granting roles to principals:\n\n- Currently, these roles use the Data Studio name.\n- Looker Studio does not support custom roles.\n- To see the individual IAM permissions that each role includes, see the [IAM permissions reference](/iam/docs/permissions-reference).\n\nBest practices\n--------------\n\nWe recommend the following best practices when you're setting up your Looker Studio Pro project:\n\n### Create a separate Google Cloud project for your Looker Studio Pro assets\n\nIt's a good idea to create a dedicated project to manage Looker Studio Pro assets. Keeping this project separate from your other projects helps make it clear what the project is used for and helps prevent accidental deletion of your assets.\n\n### Limit the number of principals on the project\n\nKeep the number of people you add to the project to a minimum. Remember, access to the project is NOT a requirement to use Looker Studio. Instead, think about Looker Studio project access as a way to delegate administrative functions to a select few individuals.\n\n### Follow the principle of least privilege\n\nIf you add people to the project, grant them the minimum role that is required to manage your Looker Studio assets according to your organization's policies.\n\nUse the roles that are specific to Looker Studio. **Don't use IAM basic roles**. Basic roles include thousands of permissions across all Google Cloud services. In production environments, don't grant basic roles unless there is no alternative. Instead, grant the most limited predefined roles that meet your needs.\n\nLearn more about how to [use IAM securely](/iam/docs/using-iam-securely).\n\nOrganization changes\n--------------------\n\nIf you've linked Looker Studio Pro to a project in one organization and later want to transfer that project to a different organization, do the following:\n\n1. [Sign in](https://admin.google.com/) with an administrator account to the **Google Admin console**.\n\n | **Note:** If you aren't using an administrator account, you can't access the Admin console.\n2. Complete the setup of the new organization in Google Cloud console.\n\n3. Migrate the original project, users, and resources from the old organization to the new organization. Learn more about [migrating projects](/resource-manager/docs/project-migration).\n\n4. [Sign in to Looker Studio.](https://lookerstudio.google.com)\n\n5. In the left navigation, click **Enterprise Admin**.\n\n6. In the settings dialog that appears, on the left, click **Project ownership**.\n\n7. In the **Project ID** field, enter your Google Cloud project ID.\n\n | **Important:** This MUST be the same project that was used by the old organization.\n8. Click **Link project**.\n\nFor other transfer scenarios, please contact [Cloud Customer Care](/support) for assistance.\n\nLimits of Google Cloud project linking\n--------------------------------------\n\n- You can link Looker Studio to only one project.\n- Once Looker Studio is linked to your project, you can't link it to another project.\n- Because Looker Studio Pro projects have a Google Cloud lien placed on them, your assets are protected from accidental deletion. However, if you manually delete the project, **ALL** assets in that project are **permanently deleted**. Be careful!"]]
