People
A person in your organization is a Slack member id, a GitHub login, a Jira account, a Linear user and an email address. Five identifiers, one human, and every tool convinced its own is authoritative.
Memnox resolves them into one person, and a great deal depends on getting it
right.
Why this is not cosmetic
Author trust is a lookup against these people. An event whose author resolves to a known person is trusted; an unrecognised or absent author is tainted.
So a failure to resolve identity does not produce a cosmetic bug. It produces a wrong trust decision, a colleague's message treated as a stranger's, or worse, a stranger's treated as reachable.
Merging
Email is the only evidence strong enough to merge on. Normalized, lowercase.
Everything else, a matching display name, a similar handle, the same avatar, is a candidate. Two people called Alex Chen are two people until an email says otherwise.
Console → People, one person expanded showing their linked provider identities
screenshot slot, save as public/screens/…png and set src
Linking by hand
Many providers do not expose an email at all, so those accounts arrive unresolved. Link them explicitly from People → the person → Link identity, choosing the provider account that belongs to them.
The unresolved accounts are listed together on the same screen, which is the fastest way to work through a new connection.
This is the single highest-value bit of housekeeping in the product. Ten minutes linking identities removes most of the confusing taint you will otherwise spend weeks explaining.
Offboarding
When someone leaves, their identities stay attached to the historical record, the evidence would be worthless otherwise, while their access is removed through SCIM or the members screen.
The two are deliberately separate. Deleting a person to revoke their access would delete the trail of what they approved.
See SSO and SCIM and Privacy and retention for erasure, which is a different and heavier operation.