CoAuthor features enhanced audit logs that provide a comprehensive record of user system activity, including project additions and removals, to ensure transparency and accountability. CAD Admins can easily access and review these logs for the current space, enabling them to efficiently monitor and manage user activity within the system.
Note: An info icon with a tooltip is visible in the Audit Logs filter area. When you hover over or click this icon, you'll see a message explaining that ALL log timestamps are shown in UTC.
How to Retrieve CoAuthor Logs:
Log into CoAuthor
Access the Admin Dashboard
Select the Audit Logs tab.
Choose the desired From and To dates.
Click the "Search" button to include the desired date range.
Click the dropdown arrow of CSV to change into PDF download format.
Click Export to download a file.
What gets captured
Every audit entry records a resource (the type of record affected), an action (what happened), and a set of detail fields that describe the context of the event.
Embedding jobs include:
Job Start — capturing the sponsor ID, project ID, source ID, source name, and section or table ID.
Job Finish — including all of the above plus the embedding ID and total execution duration.
Resources
Examples of resources that are tracked include Users, Drafts, Documents, Sponsors, Permissions, Generation Batches, and Veeva integration events.
Actions
Action | Meaning |
| Standard record operations |
| A user signed in |
| Document lifecycle steps |
| Content was exported or downloaded |
| Security-related events |
| Integration or configuration changes |
| An audit log or integration was accessed |
Detail fields
Every entry automatically includes context about who acted and what was affected:
Field | Description |
| The user who performed the action (or |
| Identifiers tying the event to its sponsor, project, document, and draft |
| The human-readable name of the affected record |
For update actions, additional fields capture exactly what changed:
Field | Description |
| The field that was modified |
| The value before and after the change |
| A short description of the change, when available |
The exact set of context fields depends on the record type. For example, a Draft event captures its sponsor, project, and document, while a Sponsor event captures only the sponsor.
Viewing audit logs
Access: The Audit Logs page is available only to users with the Administrator role. Other users are redirected automatically.
Open Admin → Audit Logs.
Choose a date range. By default, the last 24 hours are shown.
Click Search to load matching entries.
While viewing, you can:
Search within results — filter the loaded entries by text.
Filter columns — show or hide entries based on field content, or hide empty/non-empty rows.
Scroll continuously — additional records load automatically as you scroll.
Downloading audit logs
To export entries for record-keeping or external review:
Set your desired date range.
Click Search.
Set your desired download format.
Click Export.
A plain-text file is generated containing every matching entry, named with the selected range — for example, audit_logs_20260601_000000_to_20260630_235959.log.
How long logs are kept
Scope of retention: Audit logs and related application-level system activity records are actively available for review for 14 days. After this period, records are archived to secure, tamper-evident storage and retained in a non-erasable, non-rewritable format for the duration of the required retention period — they are not deleted or rotated out. Access to these records is restricted to authorized Certara personnel; if you require log data for your own internal compliance review, contact your Certara support representative.
Good to know
Audit logging never interrupts your work. If an entry cannot be written for any reason, the underlying action still completes normally.
Entries are tamper-evident. Audit logs are append-only and are not editable from within the application.
Viewing and downloading are themselves logged. Each time an administrator searches or downloads the audit trail, that access is recorded as its own audit entry.