Private Pro category · 11 compositions
Teams
People directories, leadership stories, collaboration, and recruiting. 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 11 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
People directory
Role clusters
Collaboration map
Advisers
Hiring team
Remote constellation
Project crews
Team values
Member spotlight
Organisation chart
Category contract
- Purpose
- People directories, leadership stories, collaboration, and recruiting.
- Declared dependencies
- gummy-typography, gummy-button, gummy-card
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Teams blocks
Team compositions support directories, leadership context, collaboration, and recruiting. Decide whether the page serves internal coordination or public storytelling, then include only roles, relationships, and contact details appropriate for that audience and purpose.
Drive membership and permission-sensitive actions from authorized server data. Public profiles need publication consent; internal directories need scoped visibility. Preserve useful order, filters, missing-photo fallbacks, and explicit invitation or removal outcomes without exposing private email addresses in page source.
Test empty and large teams, duplicate names, multiple roles, pending invitations, suspended members, restricted actions, and long international names. Confirm every public biography and image is approved, and never invent employee totals, leadership quotes, or customer-facing collaboration activity.
Separate public profile content from operational membership data in the handoff. Document invitation, acceptance, role change, removal, and last-owner rules, plus who may perform and observe each action. Provide safe example identities rather than real records. Public team storytelling also needs named consent and a correction path independent of account administration.
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.