Ada dua cara untuk mengupgrade laporan dan sumber data Looker Studio yang sudah ada ke Looker Studio Pro: upgrade pengguna akhir dan upgrade admin.
Upgrade pengguna akhir
Dalam upgrade pengguna akhir, tiap-tiap pengguna di organisasi memilih konten yang ingin diupgrade dan menggunakan antarmuka pengguna Looker Studio Pro untuk memindahkan laporan dan/atau sumber data mereka ke ruang kerja tim atau Sandbox pribadi mereka. Pengguna akan langsung dapat menggunakan fitur Looker Studio Pro dengan konten yang telah diupgrade.
Tips : Sebaiknya gunakan opsi ini untuk deployment kecil, seperti langganan tiap-tiap tim atau uji coba terbatas Looker Studio Pro.
Dalam pemindahan konten yang dikelola admin, administrator Google Workspace di organisasi akan menetapkan project Google Cloud default untuk Looker Studio Pro. Jika pengguna memiliki langganan Pro yang terkait dengan project tersebut, konten mereka akan dipindahkan ke lokasi Sandbox masing-masing di bagian project tersebut.
Tips : Sebaiknya gunakan opsi ini untuk deployment besar atau perusahaan.
Catatan : Saat pengguna memiliki langganan Looker Studio Pro yang dikaitkan dengan project Pro default, mereka tidak akan lagi memiliki lokasi untuk folder Milik saya. Semua konten baru yang dibuat pengguna harus berada di Sandbox atau di ruang kerja tim.
Catatan tambahan tentang cara mengupgrade konten ke Looker Studio Pro
Apa pun metode upgrade yang dipilih, informasi berikut berlaku:
Mengupgrade konten yang sudah ada tidak akan mengubah URL konten tersebut. Link ke konten akan tetap berfungsi seperti sebelum upgrade. Orang yang sudah memiliki izin lihat atau edit pada konten tidak akan kehilangan akses. Tidak ada periode nonaktif selama upgrade.
Memindahkan konten tidak akan mengganggu akses ke konten. Pengguna akan tetap memiliki akses ke laporan dan sumber data mereka selama proses pemindahan.
Pengguna mungkin akan memperoleh akses ke konten karena izin yang diwarisi melalui hierarki IAM. Misalnya, jika pengguna memiliki peran Pelihat Aset Data Studio di project Looker Studio Pro, mereka akan dapat melihat konten yang diupgrade meskipun konten tidak dibagikan secara eksplisit kepada mereka. Demikian pula, peran umum seperti Pemilik Project atau Editor Project juga akan memberikan akses ke konten Looker Studio Pro.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-31 UTC."],[],[],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."]]
