The defaults get you running, but Metabase on your server should feel like your company’s tool — your data model, your names, your branding, your security posture. The agent can do all of this through the admin panel, the API, or the config files on the box. Here are ten customizations worth asking for.

1. Clean Up the Data Model

Out of the box, Metabase shows every table and column exactly as the warehouse stores it, junk included. Have the agent hide tables nobody should see, set semantic types (currency, category, URL), and confirm foreign keys so the GUI query builder offers smart joins. Example: “Hide all tables with _tmp in the name, mark amount_usd as currency, and make sure customer_id joins to customers(id).” This one pass improves every future question anyone builds. It can also add table descriptions so hovering a name explains what it holds.

2. Build a Metrics Layer

Metrics let you define “Net revenue” or “Active customer” once, centrally, and everyone builds on the same definition. Segments do the same for reusable filters like “EU orders” or “enterprise accounts.” Example: “Create a metric called Net revenue from paid orders minus refunds, and a segment for EU customers.” When the definition changes, it changes in one place instead of across forty saved questions. This is the cheapest way to stop two dashboards from disagreeing.

3. A Shared SQL Snippet Library

Your team writes the same CTEs over and over: fiscal calendar, churn window, channel mapping. The agent can create shared SQL snippets with proper names and folders so anyone writing native SQL inserts them in one click. Example: “Turn our fiscal-calendar logic into a shared snippet called fiscal_month and organize snippets into Finance and Marketing folders.” It can also update the existing questions that pasted the old copy inline, so the logic lives in exactly one place going forward.

4. Lock Down Permissions Properly

Default access is too generous: every new user lands in a group that can poke at everything. Have the agent audit groups, grant view-only access to the collections people actually need, and strip the default group’s data permissions down to nothing. Example: “Give the Marketing group view access to the Marketing collection only, and make sure they can’t query the finance tables.” It can print the effective permissions for each group so you can see exactly who reaches what, collection by collection and table by table. Do this before your headcount doubles — retro-fitting permissions onto a messy instance is ten times the work of setting them cleanly.

5. Make It Look Like Your Company

Swap the site name, logo, favicon, and accent colors so the tool reads as yours — whitelabeling options cover the visual side, and the agent can set what your plan allows. Example: “Rename the instance to Northwind Analytics, set our logo, and make the Company overview dashboard the homepage.” It should also set the report timezone to your business zone so “yesterday” means your yesterday, not the server’s. Small change, big difference in how often staff actually open the thing.

6. Custom Region Maps

If you report by sales territory or delivery zone, the built-in country maps will not cut it. The agent can take your GeoJSON boundaries, upload them as a custom map, and wire your region column to it so dashboards get a real choropleth. Example: “Add our three delivery zones as a custom map and make the orders-by-region dashboard use it.” GeoJSON is fiddly and one malformed polygon breaks the upload — the agent can validate the file and tell you exactly which shape is broken. Once loaded, region filters click together nicely.

7. Speed Up Slow Dashboards

When a dashboard takes twenty seconds, people quietly stop using it. The agent profiles the underlying SQL, finds the filters that scan whole tables, and either adds the right database indexes or enables Metabase’s result caching with a sane TTL. Example: “Find why the Sales dashboard is slow and fix it — add indexes if the database needs them.” Insist on before-and-after timings rather than guesses. Often the real fix is a small model that pre-aggregates nightly, and the agent can build that too.

8. Harden Sign-In and Email

Self-hosted means you own the lock. Have the agent configure SMTP so invites and alerts actually send, restrict sign-ups to your email domain, and set session timeouts to something sane. Example: “Only allow sign-ups from @ourcompany.com, set sessions to expire after 12 hours, and connect email through our mail server.” If you run Google Workspace or Entra, it can set up SSO so there is one less password in circulation. None of this is glamorous; all of it matters by the second incident.

9. Move the App Database Off H2

The default install keeps everything — questions, dashboards, users, permissions — in an embedded H2 file. Fine for a trial, risky for a business you care about. The agent can migrate the application database to Postgres using Metabase’s official migration path and then verify every dashboard survived. Example: “Move the Metabase application database from H2 to Postgres on the same server, then confirm my dashboards still load.” It involves a short restart, so schedule it for a quiet evening. Afterwards, backups become a normal pg_dump instead of copying a live file.

10. Embed a Dashboard in Your Customer Portal

If customers already log into your own portal, you can frame a live Metabase dashboard inside it with signed embedding — parameters locked to that customer, no second login. The agent generates the embedding secret, builds the signed URL with a locked customer_id parameter, and hands you the iframe snippet. Example: “Set up signed embedding of the Usage dashboard so each customer sees only their own data, filtered by their account id.” It should also disable that dashboard’s public link, so there are no unauthenticated side doors. Your portal suddenly has real analytics for an afternoon of work.

None of these need a BI consultant — they need an afternoon and decent prompts. Pick the three that hurt most and ask. Metabase on OpenSysLab