[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-07-27 (世界標準時間)。"],[],[],null,["# Permissions\n\nMake permission requests simple, transparent, and understandable. When\nrequesting access, apps should make it clear why a permission is needed.\nFor more information about best practices with permissions, see\n[Request permissions on Wear OS](/training/wearables/data/wear-permissions).\n\nWatch permissions\n-----------------\n\nWhen Wear OS needs to grant permission to a watch app, it displays a dialog\nasking the user to accept or reject that permission. Apps should request\npermissions when and where it is clear why the permission is needed.\nFor example, apps may request permissions after providing information about a\nspecific permission.\n\n**Figure 1.** Examples of permissions for a fitness app.\n| **Note:** If an app or watch face requires more than one permission at a time, the permission requests appear sequentially, one after the other."]]