Walk through the visual explanation →
Person and Profile
Person describes durable professional identity. Profile is an editable presentation of that identity. Biography, public discoverability and selected professional information may change while production history continues to refer to the same person. A public profile is therefore an inappropriate sole authority for operational participation.
Production contact presentation also has its own scope. Information visible in one production should not automatically become public biography or a reusable personal contact. The identity connection does not remove privacy decisions at those presentation boundaries.
Participation is contextual
Membership answers why a person belongs to a particular collaboration context. It has a lifecycle distinct from both identity and work. A person may belong before receiving an assignment, perform several assignments, or retain participation while work changes.
The public model deliberately does not equate every production person with a software account. Professional identity, application sign-in and current participation answer different questions. The details of identity reconciliation and invitation security remain private; the explanatory boundary is enough to understand the design.
Relationships persist deliberately
Personal Roster records a retained professional relationship. Shared production work provides context for knowing someone, but the production membership itself is not that relationship. Saving a coworker is a separate operation with appropriate contact review.
This produces a path from temporary work to persistent professional context without turning every production directory into a permanent personal address book. It also lets a future production refer to the same professional identity while creating fresh participation and work.
Cost of the separation
Identity, profile and relationship projections require consistent reference handling and understandable editing surfaces. A design that separates records but gives users no explanation of where a change belongs is still difficult to operate. The architecture must preserve ownership while the interface presents the relevant context compactly.