Skip to content

Query investigation for workspace administrators

Upcoming · Not yet deployed

Find the query.
Understand what happened.

An upcoming workspace for investigating recorded queries by person, SQL, connection, time, and outcome. Find the context behind a run without executing it again.

Discuss Audit TrailsSee the preview

Planned Pro feature. Personal query history remains on every plan.

Upcoming release: the Audit Trails workspace is not yet deployed. Covers recorded queries through SyneHQ, not all database access.

A closer look at Audit Trails.

Planned interface · Illustrative data
Workspace / Audit TrailsUpcoming release · Static example

A record with context

Acme workspace · Team query history

Pro
TodayAll actorsAll outcomes3 example records
  1. MC

    Maya Chen

    Production / PostgreSQL

    SELECT region, SUM(revenue) FROM orders…

    Recorded query outcomeSuccess
  2. AM

    Alex Morgan

    Analytics / Snowflake

    SELECT customer_id FROM monthly_revenue…

    Recorded query outcomeFailed
  3. MC

    Maya Chen

    Production / PostgreSQL

    SELECT COUNT(*) FROM customers;

    Recorded query outcomeSuccess
Fictional activity recorded through SyneHQ. Administrator view shown; other members see their own records. Pro feature.

Why Audit Trails

The context behind recorded query activity.

01

Find the relevant run.

The planned viewer brings SQL, actor, connection, time, and recorded outcome into one investigation.

Query activity through SyneHQ

02

Narrow the investigation.

Search and filter the records to focus on a person, time window, connection, or outcome.

A dedicated query history workspace

03

Respect the workspace.

Team administrators can inspect team activity; other members see their own records.

Planned Pro access, scoped by role

Investigate the run behind the question

The planned viewer brings recorded query history into one searchable workspace. Narrow an investigation by actor, time, connection, or outcome, then inspect the SQL and its context.

Owners and administrators can review team records; other members see their own activity. Personal query history remains available on every plan, while this dedicated viewer is planned for Pro.

The viewer excludes result rows and credentials. A pending record means no final outcome was recorded; it does not prove a query is still running.

Before you get started

A few useful answers.

Talk through your use case
Can I use Audit Trails today?

The dedicated Audit Trails workspace is upcoming and not yet deployed. It is planned as a Pro feature. Personal query history remains available on all plans.

Does it record all access to my database?

No. It surfaces queries recorded through SyneHQ. Activity from other clients is outside its scope, and logging may have gaps. It is not a complete or tamper-proof database audit log.

Who can see the records?

The planned viewer gives owners and administrators access to team records; other members see their own activity. Result rows and credentials are excluded. Current records do not distinguish human and AI SQL executed under the same identity.

Need a clearer record of query activity?

Discuss your investigation workflow and the upcoming Audit Trails release with our team.

Discuss Audit Trails