What’s new
These are the docs for Metabase v0.64. Check out the docs for the current stable version, Metabase v0.63.

General settings

Admin > Settings > General

This section contains settings for your whole instance, like its URL, the reporting timezone, and toggles for disabling or enabling some of Metabase’s optional features. You can configure these settings by clicking the grid icon in the upper right, then going to Admin > Settings > General.

Site name

How you’d like to refer to this instance of Metabase.

Site URL

The site URL is the web address that people use to access your Metabase instance. Make sure to include http:// or https:// to make sure it’s reachable. This feature is only available for self-hosted Metabases. For customers on Metabase Cloud, check out Custom domains.

Redirect to HTTPS

By default, Metabase is served over HTTP.

To force all traffic to use HTTPS via redirect, click http:// (under the Site URL section) and select https:// from the dropdown menu.

For example, say you enable HTTPS redirect for a Metabase instance at the site URL “example.com”. When someone enters an address like example.com/data in their browser’s address bar, they’ll get automatically redirected to a secure connection at https://example.com/data.

Note: if you haven’t set up HTTPS on your server, Metabase will not let you enable HTTPS redirect. Instead, you’ll get a warning saying “It looks like HTTPS is not properly configured.”

Homepage

Set the page people see when they first log in to your Metabase. Choose between:

  • Default Metabase home: The standard Metabase homepage.
  • Dashboard: Pick a dashboard to serve as the homepage. If people lack permissions to view the selected dashboard, Metabase will redirect them to the default homepage.
  • Custom URL: Send people to a specific URL (a collection, question, dashboard, or other page). Make sure people have access to the URL. This option is only available on Metabase Pro and Enterprise plans.

Email address for help requests

This email address will be displayed in various messages throughout Metabase when users encounter a scenario where they need assistance from an admin, such as a password reset request.

Usage tracking

Send anonymous tracking data to Metabase

On self-hosted Metabases, this option determines whether or not you allow anonymous data about your usage of Metabase to be sent back to us to help us improve the product. Your database’s data is never tracked or sent.

Collect user data to display in usage analytics

Collecting user data is only available on Pro and Enterprise plans (both self-hosted and on Metabase Cloud).

You can switch on logging of IP addresses, user agents, embed path, query parameters, the values people submit when they run an action, and Metabot conversation metadata for people using your Metabase, both for people logging in directly to Metabase, and for people who view an embedded Metabase component in your app. If enabled, you can find this information in your usage analytics.

By default, collection of user data is turned off.

Friendly table and field names

By default, Metabase attempts to make field and table names more readable by changing things like somehorriblename to Some Horrible Name. This does not work well for languages other than English, or for fields that have lots of abbreviations or codes in them. If you’d like to turn this setting off, you can do so from the Admin Panel under Admin > Settings > General.

If you re-enable this setting, Metabase will run a scan against your database to review your table and column names again.

To manually label field or table names in Metabase, check out the Table Metadata section in your admin panel. Metadata in the Table Metadata can be further curated in models.

Enable X-rays

X-rays are a great way for people to get quick summary stats on your data. If these X-ray queries get too slow or expensive, you can turn them off here.

Read docs for other versions of Metabase.

Was this helpful?

Thanks for your feedback!
Want to improve these docs? Propose a change.