Basedash is the AI-native Business Intelligence platform that lets you create dashboards and understand your customers using natural language. Connect your data, describe the chart you want, and let AI generate the visualization. No SQL required.
This is the 27th launch from Basedash: AI data analyst. View more
Basedash Audit Logs
Launched this week
Native audit logs for Basedash — every sign-in, query, and configuration change is on the record, including every query the AI runs, attributed and traceable. Answer who saw what, when with one filter, stream events to your SIEM, set retention to match your policy, and pull the log through the API. Built for security reviews and enterprise rollouts, alongside SSO, SCIM, and RBAC. Your BI tool finally has a memory. Every action, on the record.
Free Options
Launch Team
Basedash: AI data analyst
@maxmusing Audit logs are one of those things nobody asks about until security review, and then suddenly they're a deal blocker. When I'm evaluating a BI vendor the question is always whether I can see who exported what, not just who logged in. Do these capture query-level detail like which fields someone pulled, or is it action-level only?
Basedash: AI data analyst
@artem_fedorovich yup! We log every query and who ran it, including if it was queried by an AI on behalf of a user.
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?
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.
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.
Basedash: AI data analyst
Audit trails in BI tools are one of those things nobody misses until compliance asks. Timely add, congrats.
Basedash: AI data analyst
Thanks @kritishpuri!