[[["เข้าใจง่าย","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 UTC"],[],[],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."]]
