Summary:
Log events for user actions name the actor only by an internal user ID (data.actor / data.userId, for example stoke_presently). Please add the actor’s email, and their identity type (user, service account or API key), to every user-performed event in external logging and the Platform Connector LOG / AUDIT_TRAIL tables.

Use case:
We stream Fivetran logs to our SIEM and alert in real time on changes to connections, destinations, users, keys and logging settings. Our change-management controls need each alert to name the person who made the change. User IDs don’t appear anywhere in the Fivetran UI, so an on-call responder can’t tell who made a change from the alert alone.

Current behavior (example from 2026-11-03 01:22 UTC, a connection credential edit in the dashboard):

{"event":"edit_connector","data":{"actor":"stoke_presently","editType":"CREDENTIALS","id":"pagerduty_preraw"}}
{"event":"edit_connection","data":{"action":"EDIT","interactionMethod":"WEB_UI","primaryResourceType":"CONNECTION","primaryResourceId":"afloat_dimmer","userId":"stoke_presently"}}

Requested behavior:
Add fields such as actor_email, actor_type (USER / SERVICE_ACCOUNT / API_KEY / SYSTEM) and interaction_method (WEB_UI / API / TERRAFORM / SYSTEM) to every user-performed event, covering at least:

1. Connections: create, edit (credentials, sync frequency, schema config), pause, resume, delete
2. Destinations: create, edit, delete
3. Users, teams and roles: invite, edit, delete, role changes, team membership
4. Keys and credentials: API key/secret create and rotate (generate_api_secret), system keys, SCIM tokens, Lake Compute tokens
5. External logging: connect_logger, disconnect_logger, update_logger, pause_logging, resume_logging
6. Account and security settings: SSO/authentication, private link, proxy agents, account settings

Current workaround and its limits:
We look up IDs through GET /v1/users/{id} or the Platform Connector USER table. This doesn’t work for real-time alerting:

• The USER table syncs about hourly, so alerts fire before the actor can be resolved.
• Deleted users can no longer be resolved, which is exactly the case an investigation cares about.
• Every log consumer has to maintain its own lookup, which adds an external dependency to a security control.