[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-05 (世界標準時間)。"],[],[],null,["# Best practices and tips for using team workspaces\n\n| **Looker Studio Pro feature**\n|\n| The features and functionality described in this page are available to Looker Studio Pro users.\n|\n| [Get Looker Studio Pro](/contact)\n\n\u003cbr /\u003e\n\nThis page describes best practices, tips, and common use cases for working with [team workspaces](/looker/docs/studio/about-team-workspaces). The information on this page will help you create and use team workspaces efficiently and confidently and share content only as necessary. This page also provides examples of common naming conventions and scenarios.\n\nCreate team workspaces with a specific purpose or focus\n-------------------------------------------------------\n\nCreate and organize your team workspaces with a specific focus or purpose in mind. This can help you achieve the following:\n\n- Keep team workspaces organized and efficient to maintain.\n- Help users more quickly and conveniently access the information they need.\n\nFor example, you could implement the following structure to keep your team workspaces organized and efficient:\n\n- One team workspace for each cross-functional project that contains shared assets\n- Separate team workspaces for each team or geography, like marketing in APAC, that contain each team's specific assets\n- Separate team workspace for reporting environments, like development, staging, or production reports\n\nFor more specific guidance, see the examples in [Common use cases for team workspaces](#common_use_cases).\n\nManage membership with Google Groups\n------------------------------------\n\nGoogle Groups can help you manage team workspace membership by automatically granting group members access to the team workspaces that the group has access to. This approach has two main advantages:\n\n- New group members have the same access to reports and data sources as do existing group members.\n- You don't have to manually configure access for each new member.\n\nShare content selectively\n-------------------------\n\nThe following tips can help you share the content within team workspaces intentionally.\n\n- **Give only the necessary permissions to each user.**\n\n When you add people or groups to a team workspace, those people will be able to create, add, and view assets within that team workspace. For people who need to also be able to add and remove team workspace members, give them the Content manager or Manager role as needed.\n- **Share individual assets for limited access.**\n\n If someone needs access to only a certain report or data source within a team workspace, you can share only that asset rather than making them a member of the team workspace.\n\nSee [Roles and permissions](/looker/docs/studio/roles-and-permissions) for more information about the different team workspace roles in Looker Studio.\n\nUse naming conventions\n----------------------\n\nTo help people find team workspaces and to avoid naming conflicts in team workspaces, agree on organization-wide naming conventions. For example:\n\n- Your company has sales divisions in different regions and you create a team workspace for each sales region. To differentiate the team workspaces, prefix them with the region or an abbreviation of the region.\n- You can indicate status by adding a prefix, such as **\\[Archive\\]** , to a project that's no longer active or **\\[In Progress\\]** to a project that's active.\n- To distinguish between team workspaces that are shared externally and those that are shared internally, add the prefix **\\[External\\]** or **\\[Internal\\]**.\n- Use labels to indicate the purpose of the team workspace, such as **\\[Pre-prod\\]** for a team workspace that contains pre-production assets and **\\[Prod\\]** for a team workspace that contains production assets. Labels can help team members understand the purpose of the workspace and what type of assets each team workspace contains.\n\nCommon use cases for team workspaces\n------------------------------------\n\nThis section includes some examples of how to use the principles outlined in this document to make effective and efficient use of team workspaces.\n\n### Example: Team collaboration\n\nSuppose you want all members of a Marketing team to have a shared space where they can create and access marketing content like reports and data sources. To create this collaborative space for the team, follow these steps:\n\n1. [Create a team workspace](/looker/docs/studio/create-edit-and-delete-team-workspaces) that is dedicated to the Marketing team's assets.\n2. [Add the members](/looker/docs/studio/manage-team-workspace-assets) of the Marketing team to that team workspace.\n3. Provide the team members with the Contributor role for the team workspace. This access will allow them to add new content and update existing assets within the team workspace.\n4. Provide leads and others who need to be able to add or remove team workspace members with the Content manager role.\n\n### Example: Production environments\n\nIn this example, suppose you have a central data team that creates content to be shared with the entire company.\n\nTo allow the team to control how their content is shared during the development process and when it's ready for production, follow these steps:\n\n1. Create a team workspace with a title like **Dev** or **Pre-prod** for content that is being developed. Pre-production content developed by a central data team can be stored in this workspace.\n2. Once the content is ready to be shared, people with the Manager role in the team workspace can move it to a production workspace. This workspace can have a title like **Prod** or **Production-specific**.\n\n### Example: Ad campaign\n\nSuppose you are working on an ad campaign for a specific client, and you want to manage all client-related content in a single place.\n\nTo do this, follow these steps:\n\n1. Create a team workspace dedicated to the client's ad campaign.\n2. Add people who are working on the ad campaign to the team workspace and assign roles based on the following criteria:\n - **Contributor role:** Members who need to be able to contribute to the project but who don't need to be able to manage member access\n - **Content manager role or the Manager role:** People who need to be able to manage access, such as the team lead\n\nThis will ensure that all relevant information is in one place and that only those who need to see it have access.\n\n### Example: Standard templates\n\nSuppose your company has published reports and metrics for different analyses, like customer support reports, marketing campaign reports, company-wide OKR reports, and project updates.\n\nYou can create templates that users can copy and customize to make it easier for people to build their own customized reports. To create a team workspace that is dedicated to standard templates, follow these steps:\n\n1. Create a team workspace dedicated to the standard templates.\n2. Move the key reports, published reports, or data sources into this workspace.\n3. Add the key people who are responsible for updating and maintaining the templates as Content managers.\n4. Add a company-wide Google Group as a viewer on the reports. This lets everyone in the company view these reports without modifying the template, as well as make use of and customize their copy of the report.\n\nThis will ensure everyone has access to the templates and that they don't make any accidental changes.\n\nRelated resources\n=================\n\n- [About team workspaces](/looker/docs/studio/about-team-workspaces)\n- [Create, edit, and delete team workspaces](/looker/docs/studio/create-edit-and-delete-team-workspaces)"]]
