用户可能会通过通过 IAM 层次结构继承的权限获得对相应内容的访问权限。例如，如果用户在 Looker Studio Pro 项目中拥有“Data Studio 资产查看器”角色，则即使未明确与其共享升级后的内容，他们也能查看升级后的内容。同样，项目所有者或项目编辑者等通用角色也将获得对 Looker Studio Pro 内容的访问权限。
[[["易于理解","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-07-31。"],[],[],null,["# Upgrade Looker Studio content to Looker Studio Pro\n\n\u003e This article is intended for users and administrators whose organization has already [subscribed to Looker Studio Pro](/looker/docs/studio/looker-studio-newsletter).\n\nThere are two ways to upgrade existing Looker Studio reports and data sources to Looker Studio Pro: end user upgrades and admin upgrades.\n\n### End user upgrades\n\nIn an end user upgrade, individual users in an organization choose the content that they want to upgrade and use the Looker Studio Pro user interface to move their reports and/or data sources into either a team workspace or their personal **Sandbox**. Users will be able to use Looker Studio Pro features with their upgraded content immediately.\n\u003e **Tip** : We recommend this option for small deployments, such as individual team subscriptions or limited trials of Looker Studio Pro.\n\nLearn how to [add and remove team workspace assets](/looker/docs/studio/manage-team-workspace-assets).\n\n### Admin upgrades\n\nIn an admin-led content move, a Google Workspace administrator in an organization sets a default Google Cloud project for Looker Studio Pro. If users have a Pro subscription associated with that project, their content will be moved into their individual **Sandbox** locations under that project.\n\u003e **Tip** : We recommend this option for large or enterprise deployments.\n\nLearn how to [set a default Looker Studio Pro project](/looker/docs/studio/set-a-default-google-cloud-project-for-looker-studio-pro). Additionally, administrators may wish to [prevent users from creating new Looker Studio Pro departmental subscriptions](/looker/docs/studio/consolidate-multiple-looker-studio-pro-subscriptions#prevent-users-from-creating-new-looker-studio-pro-departmental-subscriptions).\n\u003e **Note** : When a user has a Looker Studio Pro subscription that is associated with a default Pro project, they'll no longer have an **Owned by me** location. All new content that users create must live either in their **Sandbox** or in a [team workspace](/looker/docs/studio/about-team-workspaces).\n\n### Additional notes about upgrading content to Looker Studio Pro\n\nNo matter which upgrade method is chosen, the following information applies:\n\n- Upgrading existing content doesn't change that content's URL. Links to content continue to work as they did before the upgrade. People who already have view or edit permissions on the content won't lose access. There is no downtime during the upgrade.\n- Moving content won't disrupt access to the content. Users will still have access to their reports and data sources during the move.\n- Users may gain access to the content as a result of permissions that are inherited through the IAM hierarchy. For example, if a user has the Data Studio Asset Viewer role in the Looker Studio Pro project, they will be able to view the upgraded content even if it isn't explicitly shared with them. Similarly, generic roles like Project Owner or Project Editor will also grant access to the Looker Studio Pro content."]]
