Introducing Basedash audit logs

Today we’re launching audit logs for Basedash, a native record of everything that happens in your organization: who signed in, who viewed what, which queries ran, and how important settings changed.

For security, IT, and compliance teams, audit logs turn trust in a BI tool into something you can prove. When the security review asks who accessed customer data last quarter, the answer should take seconds and shouldn’t require an investigation.

Why analytics needs a record

Analytics touches the most sensitive data a company has. Revenue, customers, headcount, and margins all flow through dashboards and queries. As adoption grows, so does the number of people (and now AI agents) interacting with that data every day.

Many BI tools keep no record of any of it. Someone views a dashboard, exports a CSV, or changes who can query a data source, and there is no durable record that it happened. That becomes a problem as soon as a security review, a compliance audit, or an incident asks who did what, and when.

Basedash audit logs record access, queries, and configuration changes as they happen, so the answer to “who saw this?” is always in the log.

A Basedash audit log filtered to one actor, showing sign-in, table access, and export events answered in seconds.

One filter turns the log into an answer: who did what, when.

Who did what, when

The audit log is a single, chronological record of activity across your Basedash organization:

Access events: sign-ins through your identity provider, dashboards viewed, tables opened, and exports created
Query events: every query that runs against your data, whether a person or the AI ran it
Configuration events: changes to groups, permissions, data source access, and organization settings

Each event carries the actor, the action, the resource, and the timestamp. Filter by person, action, or time window to narrow the log to the events you’re asking about.

AI is on the record too

Basedash is an AI-native BI platform, so the first question security teams ask is a fair one: what is the AI doing with our data?

Audit logs make that answerable. When Basedash AI answers a question, the query it ran is logged, attributed, and traceable, including the question asked, the SQL that ran, and who the AI was working for. AI activity is held to the same standard of accountability as any analyst on the team.

An AI query trace showing the question asked, the SQL that ran, and the attribution back to the requesting user.

Every query the AI runs is logged, attributed, and traceable.

Built for the security review

Audit logs are designed to slot into the review processes and tooling your security team already runs:

Export: stream events to your SIEM or export them on demand
Retention: configure log retention to match your compliance policy
API: pull audit events programmatically through the Basedash developer platform

They join the rest of Basedash’s enterprise controls (SSO, SCIM provisioning, role-based access control, and row-level security) and complement our SOC 2 Type II compliance. Together, they cover central identity, explicit authorization, governed data access, and now a complete record of it all.

Three review-ready capabilities: export to your SIEM, retention that fits your policy, and API access to the log.

Export, retention, and API access, built for the security review.

Getting started

Audit logs are available on the Basedash Enterprise plan. Talk to the Basedash team to plan your rollout or walk through a security review together.

You can also explore Basedash’s broader enterprise controls and security model.

Roll out analytics your security team can stand behind, with every action on the record.