[[["์ดํดํ๊ธฐ ์ฌ์","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-07-31(UTC)"],[],[],null,["# Configuring alerts for Looker users\n\nLooker has several user permissions that are associated with alerts. Some permissions determine what the user can do with alerts; others determine what destinations a user can send an alert notification to. See the [Roles](/looker/docs/admin-panel-users-roles) documentation page for more information about Looker permissions, including dependencies.\n\nLooker user permissions are distinct from the alert setting called [**Permissions**](/looker/docs/creating-alerts#setting_alert_permissions), which lets the alert's creator determine whether other users will be able to view and potentially follow the alert.\n\nIn addition to the permissions that are described in the following table, users need `see_looks` permissions and `see_user_dashboards` and/or `see_lookml_dashboards` permissions for the models on which the dashboard or LookML dashboard tiles, respectively, are based.\n- Users must have permissions to access the alert's underlying content to view or explore from the alert's visualization (in the [**Alert Details**](/looker/docs/admin-panel-alerts-and-schedules-alerts#alert_details_page) page) or to navigate to its dashboard.\n- This permission does *not* grant the ability to create, follow, or delete alerts from the dashboard tile."]]
