User Identity Display

Show who someone is the same way on every screen, including when the record is gone.

moderate User Experience

What it adds

A single component that renders a person's avatar, name, secondary label, and role wherever a human is referenced.

What your agent is told to do

1
Identify every surface that names a person — assignees, comment authors, audit entries, member lists, mentions, hover cards, activity feeds — and replace each bespoke rendering with the shared component.
2
Define the fallback chain once and apply it everywhere: display name, then full name, then the email local part, then a neutral placeholder. Never fall through to a raw identifier.
3
Generate initials and a placeholder avatar deterministically from the stable account identifier, so the same person keeps the same colour and shape across sessions and screens.
4
Give the component explicit variants for account states — active, invited, deactivated, deleted — so callers pick a variant rather than each screen inventing its own way to grey someone out.
5
Do not have every instance fetch its own profile. A table of two hundred rows must resolve the people it references in one request and hand the resolved records to the component.

Edge cases it handles

Users who are deleted, still pending an invitation, or suspended must still render as something recognisable. A comment written by someone who has since left should say so plainly rather than showing a blank space or the word 'null'.
Privacy rules decide what a given viewer may see. Someone outside a workspace may be entitled to a display name and nothing else — never let an email address reach a viewer who has no right to it just because the component happened to receive one.
Long names, names that are a single very long token, and names in scripts with no spaces will all overflow. Truncate visually with the full value available on hover and in the accessible name, and never truncate mid-grapheme.
Identity must be keyed on the immutable account identifier, not the display name, so a person who renames themselves does not appear as two different people in the same thread.
Names carry scripts, diacritics, right-to-left text, and emoji. Initials derived by taking the first letter of each word will produce nonsense for some of them, so degrade to a neutral placeholder rather than a wrong initial.
System and automation actors — the scheduler, an integration, an API key — appear in the same lists as people and need their own variant instead of being dressed as a user.
Avatar images fail to load, and the fallback must occupy exactly the same box so nothing reflows when it does.

Definition of done

Every reference to a person in the app renders through the shared component.
Deleted, invited, and suspended accounts each render in a distinct, legible state rather than blank.
No field is displayed that the current viewer is not permitted to see.
The same person shows the same placeholder colour and initials on every screen and after a rename.
Long and non-Latin names truncate without breaking layout, with the full value accessible.
A list of many people resolves their profiles in bulk rather than one request per row.
A failed avatar image leaves the layout unchanged.
The feature matches the existing design system.
No existing functionality is broken.

Related features

Feedback Widget

Interactive Transcript

Relative Time Component

How it works

1

Copy the link

Grab the Markdown instruction URL for this feature.
2

Give it to your AI

Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
3

It inspects, then implements

Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.