Repository navigation
Open
Labels
admin-toolInternal tools for AAO staffInternal tools for AAO staffclaude-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.community-reportedenhancementNew feature or requestNew feature or requestmember-toolsAll member tools - profiles, dashboards, content management, working groups, eventsAll member tools - profiles, dashboards, content management, working groups, events
Milestone
Description
Summary
Users who authenticate through multiple WorkOS / OAuth connection paths or slight email variations can end up with duplicate member profile records and fragmented public community directory slugs (e.g. /community/people/username vs /community/people/username-XXXX). Currently, there is neither an automated deduplication check during account linking/provisioning nor an administrative mechanism/tool to merge orphaned records.
Problem Details
- When a user authenticates via distinct OAuth identity providers or email aliases, a second user record and distinct public slug can be created rather than associating the identity with their existing profile.
- User activity becomes fragmented: perspectives, working group memberships, committee assignments, and profile metadata are split across the two distinct accounts.
- System administrators have no tooling, database migration script, or Addie tool to safely merge the orphaned account and re-point associated foreign keys (working group memberships, authored perspectives, certifications, and org associations) to the primary account.
Proposed Solution
- Deduplication / Identity Linking Guardrails: Improve account provisioning and OAuth callback handling to detect existing verified email matches before provisioning a distinct user profile record.
- Admin Account Merge Tooling: Implement an administrative routine / endpoint to merge a duplicate account into a primary account:
- Re-assign authored perspectives, comments, and drafts.
- Re-assign working group and committee memberships.
- Re-assign certification progress and test run history.
- Re-point or clean up duplicate slug redirects.
- Safely archive or soft-delete the merged duplicate profile.
Relevant Components
- User authentication and onboarding / WorkOS callback routines
- Community profile routing (
/community/people/:slug) - Admin user management surfaces (
server/src/admin/)
Metadata
Metadata
Assignees
Labels
admin-toolInternal tools for AAO staffInternal tools for AAO staffclaude-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.community-reportedenhancementNew feature or requestNew feature or requestmember-toolsAll member tools - profiles, dashboards, content management, working groups, eventsAll member tools - profiles, dashboards, content management, working groups, events
Activity
bokelley commentedon Nov 12, 2026
Thanks for writing this up. There are two parts here, and they get different answers.
Yes: an administrative merge tool. Staff need a way to merge a duplicate member profile into the canonical one: move activity, memberships and working-group roles, redirect the old directory slug, and leave an audit record. It should be staff-only and recorded in the audit log. That's on the Evergreen backlog.
No: automatically linking identities by verified email at sign-in. We've deliberately moved away from that. Automatic Google alias consolidation was disabled (#7458) and Slack-by-email linking was contained (#7498) after #6827, because an email match alone isn't proof that two identities belong to the same person. Linking stays an explicit action by the user, or a reviewed merge by staff.
If you have specific duplicate profiles now, send the slugs and we'll merge them by hand until the tool exists.