Admins 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:

• Grant users permissions to create schedules
• Manage the scheduled deliveries created by all Looker users

Looker admins can also configure other Looker instance settings that:

• Manage the email domains to which users can deliver Looker content
• Enable the third-party integrations to which users can deliver content
• Implement an instance-wide application time zone setting or set a user-specified time zone for displaying and delivering Looker content
• Institute an instance-wide emailed data policy to restrict users to sending Looker links only, Looker data only, or both links and data for content deliveries to email
• Troubleshoot scheduling challenges

Granting scheduling permissions for users

Scheduling permissions are tied both to the type of Looker content and to the delivery destination.

See the Settings documentation page for information about scheduling permissions for embed users.

Delivery permissions for content

To deliver each type of Looker content, users need these permissions — and any permissions that those permissions depend on — for the model that the content is based on.

The table below provides permission definition summaries as they apply to delivering content. See the permissions list in the Roles documentation for complete descriptions of each permission.

Admins 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 from their user profile.

Delivery permissions for destinations

Admins 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:

• Email
• SFTP
• webhook
• Amazon S3 bucket

Looker’s third-party integrated services — also called actions — are delivered through an action hub server. A Looker admin must enable these actions from the Actions page in the Platform section of the Admin panel.

Users must have these permissions — and any permissions that those permissions depend on — assigned for the model that the Looker content is based on.

The table below provides permission definition summaries as they apply to delivering content. See the permissions list in the Roles documentation for complete descriptions of each permission.

Managing schedules created by all users

Admins can view, reassign, and delete content delivery schedules from the Schedules page and can view the history of and troubleshoot scheduled content deliveries from the 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.

Admins can also monitor what Looker content is being delivered to users with external email domains in the External Recipients section of the Scheduled Emails admin page.

Things to consider

• Content deliveries are always run on Production Mode LookML. Content deliveries cannot be set up by a user who is in Development Mode.

• Looker schedules data deliveries according to the time zone indicated in the Application Time Zone setting on the Admin Settings page, or, if enabled, the schedule creator’s User Specific Time Zone.

• If there are valid results in cache, 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.

• 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.

Known issues with content deliveries

In the Admin section of Looker, admins can use the Scheduler Plans and Scheduler History pages to look up and resolve schedule issues.

Admins 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 documentation page.

If 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 documentation page.

Certain scheduling options require that admins of customer-hosted Looker deployments have installed the Chromium renderer 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 documentation page.

See the Managing business user features page for more admin-specific information about scheduling deliveries of Looker content.