Basedash Audit Logs

The AI query attribution is the part that would actually unblock us. When someone on our team asks why a dashboard number changed, being able to pull the exact query the AI ran at a specific time is very different from guessing from logs. One thing before I connect a production workspace: does the audit log store the full query text, or just metadata like a hash or query ID? For a SIEM export use case, having the raw SQL attached to the log entry makes the difference.

The retention-follows-your-policy part is what I'd want to dig into before rolling this out on anything financial. Compliance usually forces a retention minimum, but a log full of query text can end up holding customer PII well past when a deletion request should have wiped it. Is retention global, or can specific fields get redacted before the entry is even written?

Very excited about this launch! We’ve been getting more requests for audit ability, which is a big reason why companies choose Basedash in the first place. Happy to answer any questions.

Audit trails in BI tools are one of those things nobody misses until compliance asks. Timely add, congrats.

Logging the SQL the AI ran is the necessary half. The half I'd push on is whether you store the answer it gave in words right next to the query, because a correct query with a wrong summary on top is the failure that actually reaches a decision, and nobody goes back and re-reads the SQL to catch it. Six months later the artefact a review needs is the sentence someone acted on, not just the statement that produced it.

Hey everyone, Max here from Basedash.

Today we're launching audit logs: a native record of everything that happens in your Basedash organization — who signed in, who viewed what, what changed, and every query that ran.

And especially important these days: that includes the AI. When Basedash AI answers a question, the query it ran is logged, attributed, and traceable, just like a human analyst's would be.

In practice it means the questions that used to stall a security review — "who accessed customer revenue last quarter?", "who changed permissions on this data source?" — are one filter away. Logs export to your SIEM, retention follows your policy, and the whole record is available through the API.

We've been running with it internally for months. The last time our own review asked who had touched a production data source, the answer took about ten seconds instead of a day of Slack archaeology.

Audit logs are available on the Basedash Enterprise plan today, and we're happy to walk any team through a security review this week. Happy to answer any questions.