Settings

On this Page
Docs Menu

This page outlines the configuration settings that appear on the Settings page of Looker Administration.

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.

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

Application Time Zone

The Application Time Zone is the time zone that Looker will run in. The most important impact this setting will have is determing the time zone that is used when you schedule an email or dashboard.

There are several other time zone settings in Looker which have other impacts:

  • Database Time Zone: You set this when you create a database connection. It indicates the time zone in which your database operates.
  • Query Time Zone: You set this when you create a database connection, but only if you have not enabled user specific time zones. It indicates the time zone that should be displayed to your users when they pull time data in Looker (i.e. Looker converts from Database Time Zone into Query Time Zone).
  • User Specific Time Zones: If you enable this feature, users can all set their own time zone. Looker will then convert from the Database Time Zone to each user’s time zone when they pull time data in Looker.

User Specific Time Zones

The User Specific Time Zone setting can either be enabled or disabled. If enabled, it lets users select the time zone that will be displayed to them when they pull time data in Looker. This makes it easier for employees to understand time-related data without needing to manually convert timeframes.

Looker achieves this by converting your data from the Database Time Zone, which you configure when you setup a connection, into the user’s time zone. If the user does not choose a time zone, the default will be your Application Time Zone.

When this option is enabled, Looker displays a drop-down menu in Looks, explores, and dashboards from which users can select the time zone of their query:

Options in this drop-down are:

  • Multiple Time Zones (dashboards only): All queries are run in the time zone they were saved with.
  • Viewer Time Zone: All queries are run in the user’s current time zone setting.
  • A list of every individual timezone, which users may manually choose if they like.

By default the “Viewer Time Zone” option is selected, but a Look or dashboard can be configured to default to any other item in the drop-down.

All queries default to the time zone the query was created with. In other words, if Alice creates a query with time zone “America/Los Angeles” and sends it to Bob, Bob will see the query with time zone “America/Los Angeles”, even if Bob’s time zone is set to “America/New York”. Similarly, drilling always uses whatever time zone the query was created with.

There are several other time zone settings in Looker which have other impacts:

  • Application Time Zone: This is the time zone that Looker uses when users schedule emails or dashboards.
  • Database Time Zone: You set this when you create a database connection. It indicates the time zone in which your database operates.
  • Query Time Zone: You set this when you create a database connection, but only if you have not enabled user specific time zones. It indicates the time zone that should be displayed to your users when they pull time data in Looker (i.e. Looker converts from Database Time Zone into Query Time Zone).

Load Assets from CDN

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

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

Default Visualization Colors

The Default Visualization Colors setting lets you define a default set of colors for charts, graphs, and table visualizations.

The color values can be formatted as hex strings, such as #2ca6cd, or as CSS named color strings, such as mediumblue. Simply separate the colors with a comma. Or, if you prefer to choose the color from a color picker, click on the + sign next to the boxes of colors.

Users can override these colors if they like when they create visualizations.

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 for your instance. 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 multitenant installations.

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

When the Closed System setting is enabled, non-admin users 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. Admins can still see all users and groups.

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

Email Domain Whitelist for Scheduled Looks

This setting lets you define the email domains (such as looker.com) to which your users can schedule Looker emails.

For example, if you add the domain looker.com to the email domain whitelist, scheduled emails will only be able to be sent to users that have an looker.com address. Users from other domains (e.g. gmail.com, etc) will not be able to receive emails.

If this field is left blank, there is no email domain restriction. You should also note that there is a schedule_external_look_emails permission that lets users send emails to anyone, regardless of this whitelist setting. Of course there is no need to use this permission if no one should have that ability.

New Account Notification

The New Account Notification setting can be enabled or disabled. When enabled, any Looker Admin user will be emailed when a new Looker account is created. The email will contain the new user’s email address.

URL Whitelist for Data Actions

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

For example, if you add the URL https://www.looker.com to the URL whitelist for data actions, data actions will only be able to be processed at https://www.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

If you host your own Looker instance, email addresses added to this box will receive notifications of new Looker releases.

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.

Still have questions?
Go to Discourse - or - Email Support
Top