Does iDBQuery keep audit logs of who did what?
Yes. iDBQuery keeps an audit log of key activity — who connected a source, who asked which questions, and which sensitive actions were run — so administrators can review access and reconstruct what happened. In self-hosted and air-gapped deployments the logs stay entirely inside your own environment.
Audit logging turns iDBQuery from a black box into something you can account for after the fact.
iDBQuery records the events that matter for oversight:
- Access and sign-in activity, so you can see who used the workspace and when.
- Source changes — who connected, re-synced or removed a data source.
- Questions and results, giving a trail of what was asked and what was returned.
- Sensitive or operational actions, which are gated to authorised roles and recorded when they run.
Because every iDBQuery answer is already a cited answer — each figure traced to the exact source rows it came from — the audit story goes deeper than a typical activity log: you can see not just that a report was produced, but which data it was built from. That's invaluable in an audit, an incident review, or when reconciling a number someone disputes.
Where the logs live follows your deployment. On cloud they sit in your workspace; in a private VPC, on a single on-prem server, or fully air-gapped, the audit trail never leaves your infrastructure, so you retain complete custody. Administrators can review the log to confirm access was appropriate, support internal governance, and answer "who saw this and when?" with evidence rather than assumption.
Updated 2026-06-22