Team event logs

Manage team → Logs (or Events) is an audit trail of important actions taken by members of your team. It is only shown to users who can manage the team (team.manage).

What is logged

Each row typically includes when the event occurred, which user (email), the event type, and details. Every event also records the version of Trialflare that performed it — the same short code shown in the footer of every page — so you can say which version was in use at any point in a study. The version is a column in the CSV export. Some entries expose extra popovers in the app—for example authentication payloads for API-token style actions or client metadata (browser / device context) to support investigations.

The exact event catalogue can evolve with the product; treat the log as the source of truth for “who did what, when” at team scope.

Export

Use Export logs to download a CSV of team events for offline archiving or compliance workflows. The file name is derived from your team name.

Trial-specific logs

Team logs cover organisation-wide activity. For events tied to a single trial (configuration changes, data actions scoped to that study, etc.), use the trial’s settings area in the app—Trialflare surfaces trial-level logs there so monitors can focus on one protocol without noise from the whole team.

Trial logs separate team member events from participant events, and add a Participant column: where an action was taken on a particular participant—updating their record, adding a note, assigning a pack, allocating a response—that participant’s ID is shown alongside the team member who did it. The column is included in the CSV export too.

Reading a trial's log needs trial.admin or the trial.readLogs permission — so a monitor or data manager can review the audit trail without being made an administrator. What each entry shows still follows the reader's own permissions: the values of restricted or PII data types, and participants' personal information and contact details, appear as [withheld] to a reader without the matching key, so the entry still says what happened without disclosing what they may not see. Since September 2026 a participant's creation or update is recorded by which personal fields were set (personalInformationFields) rather than their values.

Changes to who may access a trial — a permission granted or revoked, a role given, taken, changed or deleted, an account deleted — are recorded with the state before and after, so the log says what a change granted or took away. The study record (Results > Export > Study record) collects these into access/access-history.csv.

Trial logs can also be filtered to a single event type: the dropdown beside the team member / participant selector lists every type that side of the log can record, and you can type to search it. Export logs exports whatever the filter is currently showing.