Practical guide

Handle a possible duplicate member account without losing context

Last materially reviewed 2026-09-28

Quick answerConfirm the account relationship through authorised procedures before deleting or merging anything.
What to know

Treat similarity as a clue

Matching names or similar email addresses can suggest a duplicate, but they do not prove identity or establish which account should remain. Record the reported problem and relevant account route without exposing personal details in a public discussion. Do not merge records or transfer privileges solely because two profiles look alike.

What to know

Identify what each account holds

An account may contain different access, payment history, posts or administrative responsibilities. Ask the authorised owner or provider what can actually be reconciled. A display-name change is not an account merge. A migration service’s general promise does not establish that every contribution or subscription can be transferred between accounts.

What to know

Preserve a controlled decision

Use the provider’s legitimate identity and recovery process. Explain any limitations to the member before a destructive step. Record which account will be used going forward and how old entry instructions will be corrected. Avoid retaining unnecessary identity documents or sensitive screenshots in an informal volunteer inbox.

What to know

A fictional duplicate report

A volunteer signs in with a different address and creates a second profile, while the original profile holds a moderator role. The group does not grant the new profile broad permissions merely to restore convenience. It verifies the situation through the authorised process and documents the correct entry route. Until reconciliation is confirmed, the case is unresolved rather than counted as a completed member transition.

What to know

Before you close this task

Before closing the case, check the member’s future sign-in instructions and the responsibilities attached to the retained account. A resolved display-name issue may leave an obsolete invitation or a moderator role behind. Record any remaining dependency explicitly and do not describe a provider’s pending reconciliation request as a completed merge.

Continue when useful

Next: Missing access

Identify the intended space and access condition before changing accounts or asking the member to pay again.

Open Missing access →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Member purchase and access — Merchant documentation · docs.mightynetworks.com · Merchant-controlled · checked 2026-09-28
  2. Mighty privacy policy — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28