This page outlines the configuration settings that appear on the Settings page of Looker Administration.
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.
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
https:// appropriately, based on your instance’s server configuration.
Application Time Zone
When displaying data in an explore, Look, or dashboard, Looker can convert time data from the connection’s Database Time Zone to the appropriate timezone for that user.
If the User Specific Time Zones option is enabled, then an admin can set the user’s default timezone or users can set their own default timezone. If the admin or user has not set the user’s default timezone, then the Application Time Zone is used for that user. All time data will be converted from the Database Time Zone to the Application Time Zone.
User Specific Time Zones
When adding a connection, you specify what time zone your database stores time information as the Database Time Zone. However, typically users don’t know how the data is stored and simply want to use their own time zone.
If the User Specific Time Zone setting is enabled, then users can have a default time zone set by the Looker admin or by themselves. If the user does not have a time zone configured for their account, Looker will default to the Application Time Zone.
Then, when the user uses time-related filter values in a query, Looker converts filter values to the database time zone. Looker also converts the query results back to the user’s time zone. This makes it easier for users to understand and use time-related data.
When this option is enabled, Looker also displays a drop-down menu in explores, dashboards or Looks so users can override their default time zone, picking a different time zone for that query or dashboard’s set of queries:
Options in this drop-down are:
- Each Tile’s 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 time zone, 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.
If the User Specific Time Zone setting is disabled, Looker will use the Query Time Zone option, which you configure when you set up a connection.
Looker’s ability to provide time zone conversion depends on the database dialect’s ability to support this functionality. The list below shows which dialects support time zone in the most recent Looker release
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.
|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
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.
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 multi-tenant installations.
The places in Looker where users might see other users include:
- The Users page in the Admin section of Looker
- The Users Space in the Browse section of Looker, if they have been granted at least View access to another user’s personal space
- The Manage Access pop-up that is a part of Spaces management
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 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://looker.com) where your users can process data actions.
For example, if you add the URL
https://looker.com to the URL whitelist 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.
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.