Integrations/Metabase

Control what your AI agents do in Metabase.

Let your team build AI agents for Metabase. Bollard AI controls what each one can do, collection by collection.

Request early accessSee how it works →
Metabase
Dashboard Agent
Marketing CollectionOffReadFull use
Product CollectionOffReadFull use
Finance CollectionOffReadFull use
Delete questions and dashboards
What agents can do

Set what each agent can do in every collection.

Each collection gets one of three levels: Off, Read, or Full use. Anything not allowed is denied.

Off
No access
The agent can't see the collection or that it exists.
Read
Read-only
The agent can read the questions and dashboards in that collection. It can't change anything.
Full use
Create and update
The agent can create and update questions and dashboards in that collection.

Some actions stay off until explicitly turned on

Each one removes work for good or changes who can reach the data, so it could override the limits set on individual collections.

Deleting questions or dashboardsChanging data permissionsRunning native SQL
Set up & manage

Connect once. Manage everyone from there.

Connect once, then control access person by person. No new keys to hand out.

Step 1 · Set up

Connect once, company-wide

An admin connects your company's Metabase a single time and chooses which collections it covers. Any collection left out stays out of reach for every agent.

Step 2 · Manage

Control access per person and agent

From one dashboard, set what every person and their agents can reach. Change it any time, with no new keys for anyone.

OffNo access
ReadRead-only
Full useRead, create, and update questions in a single collection
Example

A dashboard building agent.

A dashboard agent builds questions in Marketing and can read Product, but it can't open the Finance collection or delete a dashboard.

Marketing CollectionOffReadFull use
Product CollectionOffReadFull use
Finance CollectionOffReadFull use

Manage access

ALLOWEDDashboard Agent updated a question in Marketing
ALLOWEDDashboard Agent read a dashboard in Product
BLOCKEDDashboard Agent tried to open the Finance collection, denied by default

Monitor activity

The security model

Top-tier security.

Bollard AI is access control for AI agents. It sits between your agents and Metabase, so they never hold your Metabase keys and never reach Metabase directly.

Everything runs through Bollard AI

Agents send their requests to Bollard AI, not to Metabase. Bollard AI checks each one against your rules and passes only the allowed requests through.

Denied by default

Every collection starts off-limits, and deleting work is held back on top of that. An agent gets in only where you've allowed it, and anything Bollard AI doesn't recognise is refused and held for review, never waved through on a guess.

Your keys stay sealed

Your Metabase keys are sealed in a vault unique to your company and never shown again. Bollard AI unlocks them only for the instant an allowed request needs it.

Activity you can read

Every attempt is recorded in plain English: who or which agent, what they tried, which collection or question, and the decision. The record is readable and can't be edited after the fact.

Questions

Metabase, answered.

Does connecting Metabase hand Bollard AI all your data?+
Only what's connected. An admin chooses which collections Bollard AI covers, and that sets the most any agent could reach. Bollard AI doesn't browse or copy your data. It sits in front of it and checks every request the agents make, passing or blocking each one.
Can an agent delete dashboards or change who can reach the data?+
Not unless you turn it on. Deleting questions and dashboards, and changing data permissions, are held off by default, so an agent can build in the collections you allow without ever removing work or exposing data, until you explicitly allow it.
Can an agent see more than the person who owns it?+
No. An agent reaches only what its owner reaches. An explicit Off always overrides an inherited permission.
Where do our Metabase keys live?+
Sealed in an encrypted vault, behind a key unique to your company. It's never shown again once connected, and Bollard AI unseals it only for the instant an allowed request needs it.
What happens when an agent tries something it's not allowed to do?+
Bollard AI blocks the request before it reaches Metabase, and the blocked attempt lands in the activity record with the reason.
How do we connect Metabase?+
An admin connects the company's Metabase once. Bollard AI seals the connection and builds the list of collections to set rules for. From then on, all management happens in the Bollard AI dashboard.
Early access

Put your team's agents to work in Metabase, without the risk.

We're onboarding our first development partners now. Tell us about your setup and we'll be in touch.

Request early accessAll integrations →