Show the members participating in a live room. Keep the roster of identities distinct from the number of open connections.
Close the extra tab and inspect what changes in the live workspace.
One person can have several connections. Show each member once, and update presence when their first tab joins or their last one leaves.
Show the members participating in a live experience.
A presence- channel uses private authorization with signed member_data. Your backend determines member_id and the safe profile information sent to the room.
After subscription succeeds, read the current member roster before applying join and leave observations. The first connection adds the member and the last connection removes them.
Every member receives member_info. Use safe display details such as a name or avatar, and keep private account fields and authorization roles out of that shared profile.
Organize teams in workspaces, control API access, and trace changes through audit logs.
HarborOrganization