Know who queried. See the SQL.
Find recorded query activity by person, SQL, connection, and time, with outcomes scoped to the workspace and your role.
Upcoming release preview. The Audit Trails workspace is not yet deployed. This Pro feature surfaces recorded query activity through SyneHQ; it is not a complete log of all database access.
Core capabilities
The right tools for
the next question.
Inspect recorded SQL, the user, target connection, execution time, and outcome for queries run through Syne.
Explore the workflowAudit Trails
Illustrative viewAuthorized administrators inspect team records. Other members see their own recorded activity.
Explore the workflowFilter and paginate records without opening each saved query. The upcoming viewer requires Pro access.
Explore the workflowAudit Trails
Illustrative viewBuilt into your workflow
A clearer account of database activity.
Plan
Pro
Context
Actor + connection
Scope
Queries through Syne
The workflow in practice
Put Audit Trails to work.
Explore the capabilities, working examples, and decisions that shape the way your team uses Audit Trails.
When a query needs a closer look, its context matters. Audit Trails brings recorded query activity into a searchable workspace: who ran it, which connection it targeted, when it happened, and the recorded outcome.
Start with the question you need to answer
Search by SQL, actor name or email, database name, or record ID. Narrow the results by time, actor, and outcome to investigate a particular run without executing the query again. The activity list and its summary counts use the same filters and access scope.
A pending record means a final outcome has not been recorded. It does not establish that a query is still running.
See the activity your role permits
Audit Trails is a Pro feature. Workspace owners and administrators can inspect team query history. Other members see their own records. Access is verified against the active workspace, and records must be attributable to that workspace's connections or other supported query targets.
Personal query history remains available on every plan. Audit Trails adds the dedicated investigation workspace and role-scoped team visibility.
Understand what the record covers
The workspace reads query logs recorded through SyneHQ. Queries run directly in another database client are outside that scope. Logging coverage and delivery can have gaps; this view does not make the underlying log complete or tamper-proof.
Human-authored SQL and AI-originated SQL executed under the same user identity are not distinguished in the current record. The audit view excludes result rows, API key secrets, and connection credentials, and provides no query execution, edit, or delete controls.
What can my team do with Audit Trails?
Find recorded query activity by person, SQL, connection, and time, with outcomes scoped to the workspace and your role.
Are these previews connected to a live database?
The examples on this page use sample data. Open SyneHQ and select your team’s configured connection to work with your own data. Controls and availability depend on your permissions and deployment.
What should I know before using Audit Trails?
Upcoming release preview. The Audit Trails workspace is not yet deployed. This Pro feature surfaces recorded query activity through SyneHQ; it is not a complete log of all database access.