The synchronization is a background process uses the refresh token of the connection owner (i.e., the person who originally created the connection) to perform all sync operations. As a result, the changeset log always shows the connection owner as the user, even if someone else actually triggered the sync. While the PlantSight portal may display the user who initiated the run, this information isn't reflected in the changeset due to how the backend handles authentication. This makes it very hard for users to audit and troubleshoot when things go wrong.