Skip to content

Affiliations and job-transition UX without authorization coupling #6819

Open

Description

@bokelley

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

Activity

  1. added this to the Evergreen milestone on Aug 24, 2026
  2. added
    enhancementNew feature or request
    websiteAny issues related to the website
    member-toolsAll member tools - profiles, dashboards, content management, working groups, events
    claude-triagingTriage routine is actively working on this issue (1-3 min)
    on Aug 24, 2026
  3. bokelley commented on Aug 24, 2026

    @bokelley
    ContributorAuthor

    Triage

    Classification: Feature request
    Bucket(s): admin / ops tools, web / site, member-tools
    Status: ready-for-human
    Milestone: Evergreen

    What the experts said:

    • internal-tools-strategist: person_affiliations schema + 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: new affiliations-db.ts + migration, modified member-profiles.ts and workos-webhooks.ts, profile view in server/public/.
    • adtech-product-expert: Core invariant (affiliation ≠ authorization) is correctly stated. Three workstreams will stall each other if bundled: data model (ready), job-transition UX copy (3 scenarios, no copy matrix — needs product sign-off), deletion policy (needs legal/privacy review). Two gaps: "active org context" switching for multi-affiliated users is unspecified; Addie MemberContext hydration invariant applies if affiliations surface in Addie responses (must add to both getMemberContext/resolveContextFromLocalDb and formatMemberContextForPrompt).

    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:

    1. Deletion/retention policy (blocker): Is there an existing legal/privacy review, or does one need to be initiated? Implementing without it creates regulatory exposure.
    2. Active org context: How is the "active" org determined for a multi-affiliated user — explicit switcher UI, last-joined, or highest-tier seat?
    3. Disputed affiliation resolution: Who has final say, what is the UI state during an open dispute, and is there an appeals path?

    Pipeline option: person_affiliations schema + 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

  4. added
    claude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.
    needs-wg-reviewBlocked on a working-group decision — surface in WG meeting agendas
    and removed
    claude-triagingTriage routine is actively working on this issue (1-3 min)
    on Aug 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    claude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.enhancementNew feature or requestmember-toolsAll member tools - profiles, dashboards, content management, working groups, eventsneeds-wg-reviewBlocked on a working-group decision — surface in WG meeting agendaswebsiteAny issues related to the website

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions