could probably be userOfPeer?.email || userOfPeer?.name || userOfPeer?.user_id || userOfPeer?.id:

• email would come first as usual
• name second as it's still user readable
• synchronized user_id from IdP (usually not readable)
• internal object id for the user (never readable)

the existing construct looks weird to me, but I didn't write JS for a decade so don't take my word on it.

I updated the code and made sure it works.

One more thing that I thought of, we should probably prefix the user_id/id with "user:" string, but I'm not sure how to type it out correctly in TypeScript or JS.

Do you mean that it will look like this in the end?

@tropnikovvl exactly what you screenshotted
on the UX side, we could end the series of ||s with "<unknown>" so it's obvious nothing was found instead of id being "undefined" string

oh, actually we shouldn't output anything at all when the user is undefined, this will simply mean there is no user attached to the peer

something like (pseudocode):

user = userOfPeer?.email || userOfPeer?.name
userId = peer?.user_id || userOfPeer?.id
if !user && userId {
	user = `user:${userId}`
}

Done
The user field will only be displayed if there is at least some ID value.

great, @heisbrot can you review and merge this?