Repository navigation
Open
Labels
claude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.Issue has been triaged by the Claude Code triage routine. Remove to re-triage.enhancementNew feature or requestNew feature or requestmember-toolsAll member tools - profiles, dashboards, content management, working groups, eventsAll member tools - profiles, dashboards, content management, working groups, eventsneeds-wg-reviewBlocked on a working-group decision — surface in WG meeting agendasBlocked on a working-group decision — surface in WG meeting agendaswebsiteAny issues related to the websiteAny issues related to the website
Milestone
Description
Summary
Represent a person's current and historical employment/consulting relationships separately from organization access, and provide a safe job-transition experience when an employer seat ends.
Core invariant
An affiliation is biographical/profile data, never an authorization grant. WorkOS organization membership and seat state remain the authority for company access.
Scope
Affiliation model
- Allow multiple simultaneous affiliations for consultants, advisors, or people with multiple roles.
- Support current and ended relationships with start/end dates.
- Record relationship type, optional title, source, verification state, visibility, and who may edit each field.
- Keep employer-confirmed facts distinguishable from person-asserted profile data.
- Preserve history without implying continued authority to represent the former employer.
Privacy and display
- Default former-employer details to private unless the person explicitly chooses public display.
- Let a person end or hide an affiliation without changing organization access.
- Define organization correction/dispute behavior without allowing an employer to erase the person's global profile.
- Cover deletion, anonymization, retention, and subject-access behavior.
Job-transition UX
- When an organization seat ends, remove that organization's permissions immediately.
- Keep the person signed into their personal account when another verified credential remains.
- Explain which company capabilities ended and which personal/community capabilities remain.
- Offer affiliation visibility/end-date controls and, separately, the personal-subscription path.
- Prompt people proactively to add a personal recovery credential through Person identity and portable state: profiles, emails, points, and recovery #3590 before a work-email loss.
Acceptance criteria
- A consultant can show multiple active affiliations while operating in one explicit organization authorization context at a time.
- Ending/hiding an affiliation does not add or remove an organization membership.
- Removing an organization membership does not erase the person, profile, reputation, or affiliation history.
- Former-employer display is private by default or requires explicit opt-in under the approved privacy decision.
- UI never labels a former employee as currently authorized to represent the company.
- Tests cover concurrent affiliations, employer departure, disputed claims, privacy changes, deletion, and rejoining a former organization.
Out of scope
- Identity and recovery-credential implementation (Person identity and portable state: profiles, emails, points, and recovery #3590)
- Organization membership/seat provisioning
- Personal subscriptions and billing (separate epic)
- Alumni/community and student product tiers
Metadata
Metadata
Assignees
Labels
claude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.Issue has been triaged by the Claude Code triage routine. Remove to re-triage.enhancementNew feature or requestNew feature or requestmember-toolsAll member tools - profiles, dashboards, content management, working groups, eventsAll member tools - profiles, dashboards, content management, working groups, eventsneeds-wg-reviewBlocked on a working-group decision — surface in WG meeting agendasBlocked on a working-group decision — surface in WG meeting agendaswebsiteAny issues related to the websiteAny issues related to the website
Activity
bokelley commentedon Aug 24, 2026
Triage
Classification: Feature request
Bucket(s): admin / ops tools, web / site, member-tools
Status: ready-for-human
Milestone: Evergreen
What the experts said:
person_affiliationsschema + visibility defaults and WorkOS seat-end UX are CLEAR. Deletion/anonymization/subject-access is a blocker — compliance scope requiring a documented retention policy before deletion code is written. Employer-confirmation write path and dispute resolution mechanism are underspecified (concern). Likely surfaces: newaffiliations-db.ts+ migration, modifiedmember-profiles.tsandworkos-webhooks.ts, profile view inserver/public/.getMemberContext/resolveContextFromLocalDbandformatMemberContextForPrompt).My take: Schema + visibility defaults + job-transition explanation screen can start now. Three decisions block the full scope — one is a compliance blocker that should not be delegated to engineering.
@bokelley — three calls needed before full implementation:
Pipeline option:
person_affiliationsschema + visibility defaults + WorkOS seat-end UX screen can start immediately while #1–3 are resolved.Triaged by Claude Code. Session: https://claude.ai/code/session_01JycMLtueWChRGEYgF1hBu8
Generated by Claude Code