Apologies for the delay. David is out of the office this week, but the development team is in the process of implementing a fix for this issue. Should be a quick fix - will let you know when it’s deployed.

Apologies for the delay. Just got an update from development, and the fix has been deployed. From their response, for clarity:
An update was made such that the engagement’s ownerId is used for displaying who created the engagement (and falls back to createdBy if ownerId is not set).
Tasks are an exception to this, because the ownerId corresponds to whoever the task is assigned to. In the tasks case, we use the createdBy for displaying who was responsible for creating the engagement.

I created two engagements with two different owners.
I see the right behavior, when I’m connected as a “simple agent”,
but it’s the wrong behavior when I’m connected as the agent who created the OAuth connection.

We can compare these two screenshots from the same contact done from two different owners’ account.

Hi Charles - it doesn’t look like these engagements are on the same contact referenced in the earlier post - if you can send a link to the contact with the new examples I’ll ask the developer to dig in. Thanks!