Problem

Organization administrators need to track and audit who creates or activates Rovo Connectors (e.g., GitHub, third-party integrations) across their sites. Currently, when a Synced Lite connector is activated — either through system-level background synchronization or organization-level behavior — the audit log records the actor as "Anonymous User" instead of attributing the action to a specific user or system process.

This makes it difficult for admins to:

• Identify who initiated a connector addition across sites in the organization
• Correlate connector events with other administrative actions

Suggested Solutions

• Display the actual user identity (or a descriptive system actor label in audit log entries for connector creation and activation events.
• If the action was triggered by a system-level process, clearly label it as such (e.g., "System - Synced Lite Auto-Activation") rather than defaulting to "Anonymous User."
• If the connector activation was inherited from another site where a specific admin performed the action, reference the originating admin and site in the log entry.

Workarounds

None available. Customers cannot currently determine who or what triggered the connector event from the audit logs alone.