Audit logs
Root users can view application event audit logs from the Admin panel Audit logs tab.
Application event audit logs are retained for 365 days by default. In Platform Enterprise, this retention period can be customized. You can also disable automatic audit log deletion with TOWER_CRON_AUDIT_LOG_CLEAN_UP_ENABLED.
Audit log versions in 26.1
Seqera Platform Enterprise 26.1 introduces the audit log v2 schema as a breaking change for direct database consumers and custom ETL jobs.
- The legacy audit log schema remains in the
tw_audit_logtable. - The new audit log v2 schema is written to a separate table.
- The v2 schema is not backward-compatible with the legacy schema. Field names, structure, and pagination behavior differ.
- The v2 Admin panel view and CSV export are available when
TOWER_AUDIT_LOG_V2_WRITE_MODEis set todualorv2.
Use TOWER_AUDIT_LOG_V2_WRITE_MODE to control how new audit events are written:
dual: Write new events to bothv1schema andv2schema. This is the recommended 26.1 migration mode if you need to validate the v2 schema while keeping existing v1 integrations unchanged.v2: Write new events tov2schema only.
Upgrade path for existing integrations
If you have existing scripts, exports, or ETL processes that read from the legacy audit log schema, plan the 26.1 upgrade in two stages:
- Upgrade to 26.1.
- Validate your integrations against the v2 schema while your existing v1 readers continue to work from the legacy table.
In the 26.1 migration plan, dual-write is transitional. Plan for 26.2 to make v2 the only write-side schema, while the legacy v1 data remains available for reads as long as your retention policy still covers the required historical period.
Audit log event format
When audit log v2 is enabled, the Admin panel shows the following event details:
- Timestamp: Event timestamp in ISO 8601 format.
- Event: The audit event name, such as
user_sign_inorcredentials_created. - Actor: Whether the event was triggered by a user or by the system, including point-in-time user details for user-initiated events.
- Client: Client IP address, user agent, and access token ID when available. Client details are empty for system-initiated events.
- Target: The resource type, ID, and resource name associated with the event.
- Organization: The organization ID and name for organization-scoped or workspace-scoped resources.
- Workspace: The workspace ID and name for workspace-scoped resources.
- Correlation ID: An identifier that links all audit events emitted as part of the same cascade action.
For organization-scoped, personal workspace-scoped, or system-wide targets, the organization and workspace columns display N/A labels to indicate when a field does not apply to that resource scope.
CSV exports use the same v2 schema and date filters as the Admin panel view. You can control the maximum export size with TOWER_AUDIT_LOG_V2_CSV_EXPORT_MAX_LOGS.
Audit log v2 events
Audit log v2 emits the following event names.
Event | Target | Description |
|---|---|---|
| Workflow run | A workflow run was launched from Platform. |
| Workflow run | A workflow run was created after Nextflow established connection. |
| Workflow run | A workflow run was updated. |
| Workflow run | A workflow run completed execution. |
| Workflow run | A workflow run was deleted. |
| Workflow run | A workflow run was permanently deleted. |
| Access token | A personal access token was created. |
| Access token | A personal access token was deleted. |
| SSH key | An SSH public key was added to a user account. |
| SSH key | An SSH public key was removed from a user account. |
| User | A new user account was created. |
| User | A user account was updated. |
| User | A user account was deleted. |
| User | A user signed in to the platform. |
| Compute environment | A compute environment was created. |
| Compute environment | A compute environment was updated. |
| Compute environment | A compute environment was deleted. |
| Credentials | Credentials were created. |
| Credentials | Credentials were updated. |
| Credentials | Credentials were deleted. |
| Credentials | Credentials were permanently deleted. |
| Action | A pipeline action was created. |
| Action | A pipeline action was updated. |
| Action | A pipeline action was deleted. |
| Organization | An organization was created. |
| Organization | An organization was updated. |
| Organization | An organization was deleted. |
| Team | A team was created. |
| Team | A team was updated. |
| Team | A team was deleted. |
| Workspace | A workspace was created. |
| Workspace | A workspace was updated. |
| Workspace | A workspace was deleted. |
| Pipeline | A pipeline was added to a workspace launchpad. |
| Pipeline | A pipeline was updated. |
| Pipeline | A pipeline was deleted from a workspace launchpad. |
| Participant | A user or team was added as a participant to a workspace. |
| Participant | A user or team was removed as a participant from a workspace. |
| Participant | A workspace participant role was changed in a workspace. |
| Member | A user was added as a member to an organization. |
| Member | A user was removed as a member from the organization. |
| Member | A member role was changed in an organization. |
| Team member | A member was added to a team. |
| Team member | A member was deleted from a team. |
| Pipeline secret | A pipeline secret was created. |
| Pipeline secret | A pipeline secret was updated. |
| Pipeline secret | A pipeline secret was deleted. |
| Dataset | A dataset was created. |
| Dataset | A dataset was updated. |
| Dataset | A dataset was deleted. |
| Dataset | Dataset content was uploaded. |
| Dataset | Dataset content was downloaded. |
| Data-link | A data-link was created. |
| Data-link | A data-link was updated. |
| Data-link | A data-link was deleted. |
| Data-link (metadata) | A data-link was hidden from the workspace. |
| Data-link (metadata) | A hidden data-link was made visible in the workspace. |
| Data-link (file) | A file was previewed through a data-link. |
| Data-link (file) | A file was uploaded through a data-link. |
| Data-link (file) | A file was downloaded through a data-link. |
| Data-link (file) | A file was deleted through a data-link. |
| Studio | A studio session was created. |
| Studio | A studio session was deleted. |
| Studio | A studio session was started. |
| Studio | A studio session was stopped. |
| Studio | A studio session was updated. |
| Studio (connection) | A user connected to a studio session. |
| Studio (connection) | A user disconnected from a studio session. |
| Studio | A studio session container build was started. |
| Studio | A studio session container build failed. |
| Studio | A studio session container build succeeded. |
| Studio | A studio session lifespan was extended. |
| Studio (SSH) | SSH authentication to a studio session succeeded. |
| Studio (SSH) | SSH authentication to a studio session failed. |
| Label | A label was created. |
| Label | A label was updated. |
| Label | A label was deleted. |
| Label | A resource label was created. |
| Label | A resource label was updated. |
| Label | A resource label was deleted. |
| Label assignment | A label was assigned to a resource. |
| Label assignment | A label was removed from a resource. |
| Managed identity | A managed identity was created. |
| Managed identity | A managed identity was updated. |
| Managed identity | A managed identity was deleted. |
| Managed credentials | Managed credentials were created. |
| Managed credentials | Managed credentials were updated. |
| Managed credentials | Managed credentials were deleted. |
| Credit info | A credit grant was modified. |
| User role | A role was assigned to a user. Note: this can happen via changes to the user's team (namely, team role changes). |
| User role | A user's role was updated. Note: this can happen via changes to the user's team (namely, team role changes). |
| User role | A user's role was removed. |
| Role | A custom role was created. |
| Role | A custom role was updated. |
| Role | A custom role was deleted. |
| IdP group | An IdP group was created. |
| IdP group | An IdP group was updated. |
| IdP group | An IdP group was deleted. |
Deprecated audit events
The following legacy event names are deprecated. Use the replacement event when one is available.
Event | Replacement |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| |
|
|
|
|
|
|
|
|
|
|
|
|
Pre and post state change capture
When enabled, audit log v2 captures full resource state snapshots or images immediately before and after each change event in JSON format. This provides a complete record of what changed and satisfies regulatory requirements (such as GxP/21 CFR Part 11). Fields that are large or that may contain sensitive values are hashed.
State snapshots increase database storage requirements. For a deployment with 2 million audit log records, the snapshots can consume between 3 GB and 40 GB depending on the events and the size and complexity of the tracked resources. Plan your database capacity and retention policy accordingly before enabling this feature.
This feature is enabled once the GxP add-on is attached to your Seqera license. Contact us to obtain the GxP add-on.