[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-07-31。"],[],[],null,["# Configuring content deliveries for Looker users\n\nAdmins play a critical role in enabling users to deliver Looker content and in configuring the Looker instance for customized content delivery. To manage users' access to and use of Looker's content delivery capabilities, admins can:\n\n- Grant users [permissions](#granting_scheduling_permissions_for_users) to create schedules\n- [Manage the scheduled deliveries created by all Looker users](#managing_schedules_created_by_all_users)\n\nLooker admins can also configure other Looker instance settings that:\n\n- [Manage the email domains](/looker/docs/admin-panel-general-settings#email_domain_allowlist_for_scheduled_content) to which users can deliver Looker content\n- [Enable the third-party integrations](/looker/docs/admin-panel-platform-actions) to which users can deliver content\n- Implement an instance-wide [application time zone setting](/looker/docs/admin-panel-general-settings#application_time_zone) or set a [user-specified time zone](/looker/docs/admin-panel-general-settings#user_specific_time_zones) for displaying and delivering Looker content\n- Institute an instance-wide [emailed data policy](/looker/docs/admin-panel-alerts-and-schedules-scheduled-emails) to restrict users to sending Looker links only, Looker data only, or both links and data for content deliveries to email\n- [Troubleshoot scheduling challenges](#things_to_consider)\n\nGranting scheduling permissions for users\n-----------------------------------------\n\nScheduling permissions are tied both to the type of Looker content and to the delivery destination.\n\u003e See the [Settings](/looker/docs/admin-panel-general-settings#sso-embed) documentation page for information about scheduling permissions for embed users.\n\n### Delivery permissions for content\n\nTo deliver each type of Looker content, users need these permissions --- and any [permissions](/looker/docs/admin-panel-users-roles#permissions_list) that those permissions depend on --- for the model that the content is based on.\n\nThe following table provides permission definition summaries as they apply to delivering content. See the [permissions list](/looker/docs/admin-panel-users-roles#permissions_list) in the [Roles](/looker/docs/admin-panel-users-roles) documentation for complete descriptions of each permission.\n\nAdmins may also choose to grant users the `see_schedules` permission, which exposes part of the **Admin** menu for users to access the list of all schedules that exist on the Looker instance from the **Schedules** and **Schedule History** admin pages. Non-admins will not be able to edit or delete schedules from these admin pages; instead, users can [view and manage their own schedules](/looker/docs/user-schedules) from their user profile.\n\n### Delivery permissions for destinations\n\nAdmins must also assign users the permissions to deliver content to specific destination types, including Looker's native delivery destinations and any third-party integrations that have been enabled for the Looker instance. Native destinations include:\n\n- Email\n- [SFTP](https://en.wikipedia.org/wiki/File_Transfer_Protocol#Simple_File_Transfer_Protocol)\n- [webhook](https://en.wikipedia.org/wiki/Webhook)\n- [Amazon S3 bucket](https://aws.amazon.com/s3/)\n\nLooker's [third-party integrated services](/looker/docs/admin-panel-platform-actions#list_of_integrated_services) --- also called actions --- are delivered through an action hub server. A Looker admin must enable these actions from the [**Actions**](/looker/docs/admin-panel-platform-actions) page in the **Platform** section of the **Admin** panel.\n\nUsers must have these permissions --- and any [permissions](/looker/docs/admin-panel-users-roles#permissions_list) that those permissions depend on --- assigned for the model that the Looker content is based on.\n\nThe following table provides permission definition summaries as they apply to delivering content. See the [permissions list](/looker/docs/admin-panel-users-roles#permissions_list) in the [Roles](/looker/docs/admin-panel-users-roles) documentation for complete descriptions of each permission.\n\nManaging schedules created by all users\n---------------------------------------\n\nAdmins can view, reassign, and delete content delivery schedules from the [**Schedules**](/looker/docs/admin-panel-alerts-and-schedules-schedule) page and can view the history of and troubleshoot scheduled content deliveries from the [**Schedule History**](/looker/docs/admin-panel-alerts-and-schedules-schedule-history) page, both accessible from the **Alerts \\& Schedules** section of the **Admin** panel. Admins should be careful about deleting or disabling a user who may be the owner of important scheduled deliveries, because such an action will also delete or disable the schedules.\n\nAdmins can also monitor what Looker content is being delivered to users with external email domains in the [**External Recipients**](/looker/docs/admin-panel-alerts-and-schedules-scheduled-emails#external_recipients) section of the **Scheduled Emails** admin page.\n\nThings to consider\n------------------\n\n- Content deliveries are always run on [Production Mode](/looker/docs/dev-mode-prod-mode) LookML. Content deliveries cannot be set up by a user who is in Development Mode.\n\n- Looker schedules data deliveries according to the time zone indicated in the [**Application Time Zone**](/looker/docs/using-time-zone-settings#application_time_zone) setting on the Admin **Settings** page, or, if enabled, the schedule creator's [User Specific Time Zone](/looker/docs/using-time-zone-settings#user_specific_time_zones).\n\n- If there are valid results [in cache](/looker/docs/caching-and-datagroups#how_looker_uses_cached_queries), Looker will deliver cached results. If there are no results or if the cached results have expired, Looker will rerun the query and cache those results.\n\n- At times, a scheduled delivery could show that it has been sent successfully but fail to reach one or more of its recipients. This could happen if the underlying model has an error, if the recipient does not have access to the data, or if there are rendering problems or page errors. The destination reports an error if it is unable to connect to the specified endpoint. If such issues occur, Looker sends the person who set up the schedule an email, which includes a link to the content, a list of the recipients it failed to reach, and more information, if available, about the problem that Looker encountered when trying to reach the recipient.\n\n### Known issues with content deliveries\n\nIn the **Admin** section of Looker, admins can use the **Scheduler Plans** and **Scheduler History** pages to look up and resolve schedule issues.\n\nAdmins should note that deleting or disabling a user may have an effect on schedules owned by that user, schedules based on content owned by that user, or schedules that list that user as a recipient. For more information about how removing user access affects content deliveries, see the [Users](/looker/docs/admin-panel-users-users#removing_user_access) documentation page.\n\nIf you encounter any problems with deliveries of large Excel files, see the discussion about managing large files in Excel format on the [Managing business user features](/looker/docs/managing-business-user-features#large_excel_files_hanging_or_not_opening) documentation page.\n\nCertain scheduling options require that admins of [customer-hosted](/looker/docs/glossary#customer-hosted) Looker deployments have installed the [Chromium renderer](/looker/docs/installation-of-rendering-software#chromium) for their Looker instance. Admins can read more about rendering image-based data formats when sending and scheduling dashboards, Looks, or Explores on the [Managing business user features](/looker/docs/managing-business-user-features#rendering_image-based_formats_delivery) documentation page.\n\nSee the [Managing business user features](/looker/docs/managing-business-user-features#delivering_content) page for more admin-specific information about scheduling deliveries of Looker content."]]