Private Pro category · 9 compositions
Profiles
People, organisation, account, and public identity compositions. These records are manifest-derived and source-free; an implemented status does not imply manual verification, release readiness, entitlement protection, or availability for purchase.
Manifest items
All 9 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
Public maker profile
Team member detail
Organisation profile
Contributor card wall
Activity and access
Billing owner summary
Security settings
Profile completion
Category contract
- Purpose
- People, organisation, account, and public identity compositions.
- Declared dependencies
- gummy-avatar, gummy-badge, gummy-tabs
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Profiles blocks
Profile compositions cover people, organisations, accounts, and public identities; choose one only after identifying which fields are genuinely appropriate to display. Separate editable account controls from public presentation so privacy and authorization expectations stay clear.
Source identity, role, membership, and contact values from authorized records, with safe fallbacks for missing imagery and optional biography. Use informative image alternatives, protect mutation routes on the server, and never make hidden private fields discoverable through markup or client state.
Test absent, long, international, and bidirectional names; multiple roles; deactivated accounts; restricted fields; and image failure. Confirm who may view or change each value, how deletion propagates, and that demonstration people cannot be mistaken for actual customers or employees.
Prepare a visibility and mutation matrix for every field, including where the value originates, who can edit it, who can see it, and how correction or deletion propagates. Provide neutral fallbacks that reveal no restricted attribute. The design handoff must not contain copied production records, even when realistic content would make the composition easier to evaluate.
Boundary
Public pages contain only approved names, purposes, dependency aliases, requirements, status, and any future reviewed image preview. Editable paid source, test paths, release locations, and entitlement details remain private.