選擇內容分享方式
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
本頁說明開發人員在分享受控內容存取權時，應遵守的最佳做法。您可以在協作活動開始前或進行期間更新權限。
強烈建議您採用可盡量減少使用者摩擦或中斷的方法。開發人員應在應用程式存取控管模型和安全防護需求，以及任何使用者中斷之間，維持適當的平衡。
以下提供幾種方式，可讓使用者存取協作活動。
授予臨時存取權杖 (建議)
臨時 (會過期) 存取權杖會提供使用者在指定時間內有效的存取權和安全憑證。詳情請參閱「設定臨時存取權」。
這個方法對使用者的干擾最少。只要有連結和臨時存取權杖，任何人都能存取內容。使用者只能在權杖指定的時間內存取，權杖會在啟動者開始活動時產生。
您可以使用活動啟動狀態分享權杖。代碼可用於兌換臨時內容存取權。臨時存取權杖與內容建立時間無關。這項方法適用於新內容和現有內容。
下表列出使用這種方法的優缺點：
| 優點 |
缺點 |
| 盡量減少使用者操作障礙 |
過度分享內容的風險 |
| 允許使用者在活動開始後加入 |
|
| 不需要事先瞭解參與者 |
|
在活動開始前分享
另一種做法是設計 Meet 外掛程式，在活動開始前提示啟動活動的使用者更新權限。
下表列出使用這種方法的優缺點：
| 優點 |
缺點 |
| 明確分享可將風險降到最低 |
判斷參與者可能很困難 |
|
核准存取權時，使用者加入會議的過程會遇到中等程度的阻礙或中斷 |
隨選分享
這是被動式做法，使用者要求存取內容時，活動發起人會即時核准要求。如果無法正確判斷參與者，這個方法可能會造成使用者摩擦。因此最不建議使用。
下表列出使用這種方法的優缺點：
| 優點 |
缺點 |
| 不需要事先瞭解參與者 |
造成高摩擦力，並中斷會議流程 |
| 明確分享可將風險降到最低 |
活動開始後，需要更新內容權限的路徑 |
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-29 (世界標準時間)。
[null,null,["上次更新時間：2025-08-29 (世界標準時間)。"],[],[],null,["# Choose a content sharing method\n\nThis page describes the best practices developers should observe when sharing\naccess to controlled content. Updates to permissions can be done either before a\ncollaborative activity starts or while it's ongoing.\n\nIt's strongly recommended to implement a method that creates the least amount of\nuser friction or disruption. Developers should maintain a balance between the\nconstraints in the app's access control model and security requirements, and\nany user disruption.\n\nThe following are several ways to provide access to collaborative activities.\n\nGrant temporary access token (recommended)\n------------------------------------------\n\nA temporary (expiring) access token provides a user's access and security\ncredentials that are valid within a specified period of time. For more info, see\n[Configure temporary access](https://cloud.google.com/iam/docs/configuring-temporary-access).\n\nThis approach provides the least user friction. The content is accessible to\nanyone with the link and the temporary access token. Users only have access for\nthe duration of time specified in the token, which is generated once the\ninitiator starts the activity.\n\nYou can share a token using the [activity starting\nstate](/workspace/meet/add-ons/guides/collaborate-in-the-add-on). The token can be\nredeemed for temporary content access. The temporary access token is independent\nof the time the content is created. This approach works for new and existing\ncontent.\n\nThe following table shows the advantages and disadvantages of using this\napproach:\n\n| Advantages | Disadvantages |\n|---------------------------------------------------------|-----------------------------|\n| Least amount of friction for users | Risk of oversharing content |\n| Allows people to join after activity started | |\n| Doesn't require knowledge of participants ahead of time | |\n\nShare before activity starts\n----------------------------\n\nAn alternative approach is to design your Meet add-on\nto prompt the user starting the activity to update permissions before beginning.\n\nThe following table shows the advantages and disadvantages of using this\napproach:\n\n| Advantages | Disadvantages |\n|----------------------------------|----------------------------------------------------------------------------|\n| Explicit sharing minimizes risks | Determining participants can be challenging |\n| | Medium amount of friction or interruptions approving access as people join |\n\nShare on-demand\n---------------\n\nThis is a reactive approach where the activity initiator approves requests in\nreal-time as users request access to the content. This method might cause high\nuser friction if participants aren't correctly determined. Therefore, it's the\nleast recommended.\n\nThe following table shows the advantages and disadvantages of using this\napproach:\n\n| Advantages | Disadvantages |\n|---------------------------------------------------------|------------------------------------------------------------------------------|\n| Doesn't require knowledge of participants ahead of time | Triggers high friction and interrupts the flow of the meeting |\n| Explicit sharing minimizes risks | Requires a path to update the content permissions after activity has started |"]]
