Skip to content

Umbrella: person continuity across jobs, affiliations, and personal membership #6814

Closed as not planned
0 of 3 issues completed
Closed as not planned

Description

@pkras

Summary

Track the work required for a person to keep their identity, profile, reputation, and appropriate personal access across email and employer changes while keeping company authorization strictly organization-scoped.

This began as one proposal, but it contains independent identity, affiliation, billing, and membership-product decisions. Those tracks now have separate owners and acceptance criteria.

Non-negotiable boundaries

  • A person identity links verified credentials and person-owned state; it is not an organization entitlement source.
  • An affiliation records employment/consulting history; it never grants access.
  • Organization memberships, seats, roles, and employer-paid capabilities remain scoped to the selected organization.
  • Personal subscriptions grant only their defined person-level capabilities.
  • Aggregated person views retain source provenance and respect cross-surface privacy.
  • A durable person record remains subject to deletion/anonymization and retention policy.

Workstreams

Deferred product decisions

These should be evaluated independently after the foundations above; they do not belong in the identity schema:

  • Free alumni/community offering and its capabilities
  • Whether job loss defaults to free community access, a paid offer, or both
  • A student tier and its verification method

Recommended delivery order

  1. Finish Person identity and portable state: profiles, emails, points, and recovery #3590's ownership model and verified personal recovery path.
  2. Establish explicit capability resolution for personal versus selected-organization access.
  3. Add affiliation history and job-transition UX against those stable boundaries.
  4. Test alumni/student offerings as product changes, not identity prerequisites.

Done state

  • A person can change verified credentials or employers without losing person-owned profile/reputation state.
  • Employer departure removes employer authorization immediately.
  • A verified personal sign-in remains usable when available.
  • Personal subscription access survives employer changes without leaking access between organizations.
  • Current and former affiliations are represented with explicit visibility and no authorization semantics.

Supersedes the original combined A→E discussion scope. The linked issues are the implementation authorities.

Activity

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

    @bokelley
    Contributor

    Triage

    Classification: Discussion / proposal
    Bucket(s): member-tools, website
    Status: ready-for-human

    What the experts said:

    • internal-tools-strategist: the person-identity core of this belongs folded into Person identity and portable state: profiles, emails, points, and recovery #3590; Company + time-bound Affiliation + person-level billing is a separate multi-quarter program dressed up as "step D," and three unresolved product questions (default tier, student verification, alumni policy) should not get baked into schema before they're decided.
    • adtech-product-expert: the Person / Company / time-bound Affiliation split mirrors how ad-tech careers actually move (agency → holdco → brand → consultant → in-house) and is the right foundation; tier proliferation and Stripe-on-Person are separable follow-ons, not gating decisions.
    • security-reviewer: authz today collapses to one active org per session — multi-affiliation, self-verified student tier, and person-owned Stripe each need an explicit design pass before schema lands (per-affiliation ACLs on the collapsed member-context; Stripe scoped to identity_id rather than any workos_user_id that ever linked to it; a paid student verifier rather than .edu-alone).

    My take: Steps A/B (finish migration 460_identities.sql, email ownership) are already the #3590 charter and shouldn't fork off. Steps C/D (time-bound Affiliation, portable reputation, person-level billing/tiers) are a real successor epic — but the three open product questions need answers before columns land.

    @bokelley, your call — how do you want to scope this against #3590?

    Option A — fold identity work into #3590, keep #6814 for the additive scope:

    - #6814: Phase A (finish 460) + B (email ownership) + C (Affiliation) + D (person-billing) + E (merge)
    + #3590: Phase A + B + E   (identity / linking / merge — already the charter, 5 sub-issues)
    + #6814: Phase C + D       (time-bound Affiliation, tiers, Stripe-on-Person; depends on #3590)

    Cleanest separation; #3590 stays the identity truth, #6814 becomes the billing/tier epic that depends on it. Keeps the existing #3590 security review, no fuzzy auto-merge rule, and cross-surface privacy fence work intact.

    Option B — keep #6814 as-is, absorb #3590:

    - #3590: identity-linking epic (Evergreen, 5 open sub-issues, claude-triaged)
    + #6814: full A→E sequence, subsumes #3590

    Simpler ownership if you'd rather drive one epic; costs #3590's sub-issue history and the security review already on that thread, and re-litigates the "no auto-merge / credentials bound to originating workos_user_id" contract that's already ratified there.

    Also needs a ruling before any schema lands:

    1. Default tier when no company pays — free alumni (retention-first) or paid individual (revenue-first)? Both experts recommend offering both rails; the ask is which is default on job-loss.
    2. Student verification — product-expert says .edu + 2-year time-box is right at AAO scale; security-reviewer says .edu alone is spoofable (disposable-domain services, post-graduation carryover) and prefers SheerID storing only a token + expiry. Cost vs. robustness tradeoff.
    3. Alumni disclosure default — "Champion at $OldCo" surfaces former-employer signal (GDPR right-to-erasure edge). Default private per affiliation with opt-in public display, or the reverse?

    Triaged by Claude Code. Session: https://claude.ai/code/cse_01RJVoZC4khUTtCvSX1SZ2KR


    Generated by Claude Code

  4. added
    claude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.
    and removed
    claude-triagingTriage routine is actively working on this issue (1-3 min)
    on Aug 24, 2026
  5. changed the title [-]Person-centric profiles: retain members across jobs, multi-company, multi-email, individual/student tiers[/-] [+]Umbrella: person continuity across jobs, affiliations, and personal membership[/+] on Aug 24, 2026
  6. bokelley commented on Aug 24, 2026

    @bokelley
    Contributor

    Split completed:

    Within #3590, portable reputation is #6816 and self-service verified recovery credentials are #6817. The first ownership/provenance contract is now in review in #6820.

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, eventswebsiteAny issues related to the website

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions