home User Guide Getting Started Help Center Documentation Community Training Certification
Looker keyboard_arrow_down
language keyboard_arrow_down

The Settings page in the General section of the Admin menu lets you configure the instance-wide settings for Looker.

License Key

The license key is unique to the Looker instance you’re using. It enables or disables certain Looker features based on your licensing agreement.

The license key is hidden by default. Click Show to display the license key.

Host URL

The Host URL is the base portion of your Looker instance’s URL. It is used specifically when links to your instance are created in scheduled emails and in all absolute URLs that Looker generates.

Make sure the Host URL uses http:// or https:// appropriately, based on your instance’s server configuration.

Changing the Host URL may affect the functionality of some Looker features. See the What happens if the URL changes for my Looker instance? article in the Looker Help Center for more information about changing instance URLs.

Application Time Zone

When displaying data in an Explore, a Look, or a dashboard, Looker can convert time data from the connection’s Database Time Zone to the appropriate time zone for that user.

If the User Specific Time Zones option is enabled, then an admin can set the user’s default time zone or users can set their own default time zone. If the admin or user has not set the user’s default time zone, then the Application Time Zone is used for that user, and all time-based data queried by that user will be converted to the Application Time Zone.

The Application Time Zone setting is also used as the default time zone for scheduling data deliveries. The time zone used for schedules does not affect time data returned by a query, it only affects the time the data will be sent.

See the Using Time Zone Settings documentation page for more information.

User Specific Time Zones

When adding a connection, you specify what time zone your database stores time information as the Database Time Zone.

When User Specific Time Zones is enabled, each user is assigned a time zone, and Looker converts time-based data from the Database Time Zone to a user’s time zone when viewing query results or interpreting filters.

When User Specific Time Zones is disabled, Looker converts time-based data for all users to the Query Time Zone value.

See the Using Time Zone Settings documentation page for more information.

Load Assets from CDN

CDN stands for “content delivery network.” A CDN is a network of servers that stores content in multiple geographic locations to reduce page load time for users. Your data is never stored on these servers; only items specific to Looker (such as images) are stored here.

The Load Assets from CDN setting can be either enabled or disabled. When it is enabled, Looker pages should load faster.

This option is available only for customer-hosted instances. Looker-hosted instances always load assets from the CDN.

Default Visualization Colors

The Default Visualization Colors setting lets you define a default color collection for visualizations, and also lets you create new color collections for use in your instances.

Setting a Default Color Collection

Each Looker instance must have a default color collection.

To set a pre-existing color collection as your default, choose the color collection from the drop-down menu and click the Update button.

You can see the first categorical, sequential, and diverging palettes of each collection directly under the drop-down menu. These are the palettes that will be used as the visualization defaults. To view all the palettes in the color collection, visit the Color Collections documentation page.

Creating a Custom Color Collection

To create a custom color collection:

  1. Select Create a color collection from the collection drop-down.
  2. Give your new collection a unique name.
  3. Click each palette to edit.
  4. Select individual colors to edit, or click Edit All to edit all the colors at once.
  5. When you’re finished editing your new collection, click Update.

Color values can be formatted as hex strings, such as #2ca6cd, or as CSS color names, such as mediumblue. Or you can click on the color wheel to open and select a shade from the color picker. If you choose to edit all colors, use a comma between each color name to separate them. To add or remove a color, click on the + or - signs.

The new collection will automatically become the instance default, but you can choose a different default if you wish.

Collection IDs and palette IDs for any new custom color collections are based on each collection’s name. This allows LookML dashboards using those collections to render consistently across instances if both instances have the same custom collections named identically.

Deleting a Custom Color Collection

You can delete a custom color collection by selecting the collection from the drop-down menu and clicking the Delete button that appears. You cannot delete Looker’s native color collections.

Default Export Format

The Default Export Format setting lets you choose the default file format that is used when users choose to download data. Users can still choose a different file format if they like.

Format File Extension Description
TXT .txt A text file delimited by tabs
Excel Spreadsheet .xlsx The format for Microsoft Excel 2007 and later
CSV .csv A text file delimited by commas
JSON .json Will generate a JSON file with 1 record per line
HTML .html Will use basic HTML to display the data in a similar way that users see it in their browser. However, Looker’s CSS will not be included, so the formatting is not exactly the same.
Markdown .md Will generate a standard markdown file with a | delimited table

Public URLs

The Public URL setting can be enabled or disabled. When enabled, Looker users with appropriate permissions can generate public URLs to access Looker data.

Although public URLs are not guessable, anyone who has one can access your data without security restraints. Please use with caution.

Closed System

This option must be enabled by Looker; contact Looker Support to get started.

The Closed System setting is used in conjunction with groups to prevent users in one group from knowing about the users in another group. This is often useful for multi-tenant installations.

The places in Looker where users might see other users include:

When the Closed System setting is enabled, non-admin users who do not have the see_users permission will only be able to see other users with whom they share a group. They will also only be able to see groups of which they are members.

All admins and any users who have been granted the see_users permission can see all users and groups on the instance.

Admins can override the Closed System setting by allowing a user to see the personal folder of another user with whom they do not share a group, so please use caution when editing folder visibility.

Email Domain Allowlist for Scheduled Content

This setting lets you define the email domains to which your users can send or schedule data deliveries or alert notifications via email. Enter allowable email domains in the format domain.suffix to limit external emails per the permissions overview below. For example, to limit external emails to the gmail.com and friendly_domain.org domains:

This setting applies to all data deliveries: Looks, dashboards, queries with visualizations, and alerts.

Permissions Overview

A user must have at least the schedule_look_emails permission in order to email any Looker content. To send alert notifications, a user must also have create_alerts permissions.

Some users may additionally have the schedule_external_look_emails permission, which can be granted if the user first has the schedule_look_emails permission (see more on permissions and dependencies on the Roles documentation page).

Permissions and Considerations for SSO Embed Users

An embed user must have at least the schedule_look_emails permission in order to email any Looker content. To send alert notifications, a user must also have create_alerts permissions.

Some embed users who additionally have the schedule_external_look_emails permission can send email data deliveries to any email address, regardless of the configuration of the Email Domain Allowlist for Scheduled Content field.

Due to the nature of embedding content, there are some circumstances that are different for embed users as opposed to non-embed users. Embedded Looker content is accessed through a dedicated embed user account, not by individual user accounts. Therefore, when a person accesses Looker content through an embed, Looker isn’t expected to know the individual user’s email address. Because of this, embed users with only the schedule_look_emails permission are allowed to email Looker content only to emails with domains listed in the allowlist. This means that:

There is one exception to these rules:

You can provide Looker with an embed user’s email address by defining it in the email user attribute in the SSO embed URL. For example:

If you define the email user attribute in the embed URL, Looker will allow an embed user with just the schedule_look_emails permission to email Looker content to their own email address, even if their domain isn’t in the Email Domain Allowlist for Scheduled Content field, or if the Email Domain Allowlist for Scheduled Content field is blank.

New Account Notification

The New Account Notification setting can be enabled or disabled. When it is enabled, any Looker admin user will be emailed when a new Looker account is created. (SSO embed users are an exception; emails are not generated when an SSO embed user is created.) The email will contain the new user’s email address.

URL Allowlist for Data Actions

This setting lets you define URLs (such as https://looker.com) where your users can process data actions.

For example, if you add the URL https://looker.com to the URL allowlist for data actions, data actions will only be able to be processed at https://looker.com. Attempts to process data actions at other URLs will not be allowed.

If this field is left blank, there are no URL restrictions for data actions. However, if you have included a user attribute in a data action, this field is required. In that case, you must provide valid URLs to process data actions.

Technical Contacts

Email addresses added to this box will receive notifications of security updates, major bug fixes, and new Looker releases. They will also have visibility into all support requests submitted by members of their organization in the Customer Portal in the Looker Help Center.

Looker Support requires permission from a technical contact to do any of the following:

Outgoing Webhook Token

If a user schedules a Look to make a webhook request, the request will include a special Looker token that can be set here. This token can then be used to verify the legitimacy of webhook requests.

In-App Guides

In-app guides let Looker communicate with users in the application via tutorials, banners, alerts, and surveys. These communications are used to help users get more out of the platform, alert them to new features, get feedback on the platform, and invite users to trainings and events where they can learn how to better use Looker.

Administrators can choose to disable guides for their instance, which will disable the guides for all users on the instance. There is no way to selectively turn off in-app guides for certain users. Looker will not show in-app guides to embedded users or users on whitelabeled instances.

Guides are designed and deployed by Looker’s Customer Experience team and will change over time. Looker serves the third-party software (Pendo) JavaScript. The individual guides are vetted and allowlisted by Looker. When fetching a guide from Pendo, Looker validates that the guide is unchanged using sha256 integrity hashes. If there are any changes to the guide after Looker’s review, Looker prevents use of the changed guide. If a user’s browser cannot reach the Pendo server, then the guide is simply not displayed.

Cookie Notification Banner

When enabled, this setting will show a cookie notification banner to all users on your instance. By default this setting is disabled.

We recommend enabling this setting if you need to comply with the European Union’s data protection regulations.

Use Gravatar

When enabled, this setting displays the Profile Picture option on the user menu, letting users select or create an avatar for their account using the Gravatar app.

Curated Search

Curated Search does not apply to closed systems but is otherwise enabled by default.

When Curated Search is enabled, users are able to search for content across shared folders, their personal folder, and boards. Content that is saved in other users’ personal folders will be included in the results only if such content is also pinned to a board. The search results will exclude content that exists only in the personal folders of other users. Users have the option to exclude content in personal folders by clicking the switch next to the Curated Search feature name in the search modal.

PCI — Track SQLRunner and Dev Queries

Available only with the Looker for PCI product offering, when this setting is enabled, Looker generates an event when a user issues a query using SQL Runner and generates an event when a user issues a query while in Development Mode.

PCI — Send Events to Syslog in Common Event Format

Available only with the Looker for PCI product offering, when this setting is enabled, Looker sends all system events to syslog in the Common Event Format (CEF) in addition to storing them in the System Activity database. You can view information about specific events in the System Activity Event and Event Attribute Explores.

PCI — Scan Query Results for Credit Card Numbers

Available only with the Looker for PCI product offering, when this setting is enabled, Looker will scans all query results for cardholder data (in this case, credit card numbers) and generate an event in the System Activity database when possible primary account number (PAN) data is detected. You can view information about specific events in the System Activity Event and Event Attribute Explores. Enabling this seting can affect instance performance.