Skip to content

Identity privacy fence: consent and authorization rules for cross-surface linking #6491

Open

Description

@bokelley

Split from #3590.

Decision needed

Define when data from one linked identity may be used on another surface or in another organization context.

Acceptance criteria

  • Rules cover Slack, web, email, billing, certification, and admin views.
  • Organization boundaries and purpose limitation are explicit.
  • Sensitive fields have field-level allow/deny behavior.
  • User-visible link/unlink and consent behavior is defined.
  • Audit, retention, deletion, and subject-access behavior are specified.
  • Security/privacy review approves the fence before any MemberContext collapse ships.

Activity

  1. added this to the Evergreen milestone on Aug 13, 2026
  2. added
    enhancementNew feature or request
    addieIssues related to Addie (via any channel)
    admin-toolInternal tools for AAO staff
    claude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.
    on Aug 13, 2026
  3. added
    needs-wg-reviewBlocked on a working-group decision — surface in WG meeting agendas
    on Aug 13, 2026
  4. added
    triage:archive-reviewInactive 30+ days; human keep/close review required (not automatic closure)
    triage:outcome-missingclaude-triaged label is present but no visible triage outcome comment was found
    on Sep 21, 2026
  5. bokelley commented on Sep 21, 2026

    @bokelley
    ContributorAuthor

    Maintainer triage — 2026-09-21

    Classification: Privacy architecture decision

    Status: Ready for human decision

    Decision: Establish an explicit identity privacy fence before collapsing MemberContext or exposing linked identities.

    Next gate: Security/privacy owners define organization isolation, allowed joins, auditability, retention, and erasure behavior.

  6. removed
    triage:archive-reviewInactive 30+ days; human keep/close review required (not automatic closure)
    triage:outcome-missingclaude-triaged label is present but no visible triage outcome comment was found
    on Sep 21, 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

    addieIssues related to Addie (via any channel)admin-toolInternal tools for AAO staffclaude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.enhancementNew feature or requestneeds-wg-reviewBlocked on a working-group decision — surface in WG meeting agendas

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions