Skip to content

Personal subscription continuity across employer and credential changes #6818

Open

Description

@bokelley

Summary

Preserve a person's individual subscription and personal capabilities across employer and credential changes without turning identity linkage into a source of organization authorization.

Individual Professional and Explorer subscriptions currently use a one-person is_personal = true organization because Stripe customers, subscription state, tier resolution, and feature gates are organization-centric. That implementation can remain the compatibility boundary initially; the missing piece is making the personal workspace durable and discoverable through the person's identity.

Direction

  • One durable identity owns or controls one persistent personal workspace/billing account.
  • Existing Stripe and subscription records remain attached to that billing boundary during the first phase; do not require a Stripe-on-Person rewrite to solve continuity.
  • Employer-paid seats remain scoped to the selected organization.
  • Personal entitlements apply only to the person and only for the capabilities included in the personal tier.
  • Capability resolution is explicit; it does not union permissions from every organization the person can access.

Scope

  1. Define an entitlement matrix for:
    • global free/community capabilities
    • personal Explorer/Professional capabilities
    • organization-seat capabilities in the selected organization
  2. Associate and resolve the persistent personal workspace through identity_id, regardless of which verified credential is used to sign in.
  3. Reconcile existing personal workspaces and subscriptions to the correct identity with conflict reporting and no email-only billing reassignment.
  4. Update checkout, invoices, webhooks, lazy reconciliation, membership context, and feature gates to use the durable personal-workspace relationship.
  5. When an employer seat ends, immediately remove employer-scoped access and clearly show the remaining free or personally paid capabilities.
  6. Offer an individual upgrade path without implying that profile or reputation was lost.

Security and billing invariants

  • Linking a credential or affiliation never grants an employer's seat or role.
  • Entitlement checks use the authenticated identity plus an explicit selected-organization context.
  • A Stripe customer/subscription is never reassigned from an email match alone.
  • Employer offboarding cannot cancel or take ownership of the person's separate personal subscription.
  • Refunds, cancellation, tax records, invoices, and audit history retain their original billing provenance.

Acceptance criteria

  • A person with an active personal subscription receives the same personal capabilities through every verified linked credential.
  • A person may belong to multiple organizations, but requests operate in one explicit organization context and never inherit a privilege union.
  • Ending an organization membership removes its access immediately while preserving personal-workspace access.
  • Existing individual subscribers migrate/reconcile without duplicate Stripe customers, duplicate subscriptions, or silent ownership changes.
  • Checkout/webhook/invoice tests bind subscription state through server-issued identifiers, not customer-supplied email.
  • MemberContext and UI distinguish AgenticAdvertising.org membership, organization membership, organization seat, and personal capability source precisely.

Out of scope

Dependencies

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): member-tools, admin / ops tools, security-sensitive
    Status: deferred

    Blocked-on: #3590 (durable identity foundation), #3589 / #6492 (billing attribution hardening) — resurfaces on merge.


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


    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
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

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions