Stop duplicate user identities from undermining access removal
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
Removing the account you recognise is not enough if the same person also has an older account, an alternate email address, or an outstanding invitation. To audit duplicate workspace user accounts, reconcile every account and invitation against a current staff roster, establish who controls each identity, decide which access is authorised, and verify closure of every redundant route.
The unit of review should be the person and all their workspace identities, not a single row in the user list. A familiar name marked inactive does not establish that the person has no remaining access.
This review concerns staff identities and their permissions. It is not a customer-contact deduplication exercise, an identity-provider implementation project, or a reason to merge customer records.
1. Build a person-to-access inventory before changing accounts
Start with two inventories: the current staff roster and the workspace's user and invitation records. Add approved contractors or other authorised collaborators to the roster if they are not already represented. Someone absent from an employee list is not automatically an intruder; their access still needs an accountable sponsor and a documented purpose.
For each person, record a stable internal reference, employment or engagement status, manager or sponsor, current work address, and known former work addresses. Use only information needed for the review, and keep the worksheet restricted because it connects people to access rights.
For each workspace identity, capture the account reference if available, displayed name, exact email address, status, role, relevant team or workspace memberships, and any pending invitation. Record who invited the account and who owns the access decision where that information is available. Recent activity can guide investigation, but inactivity does not prove that access is absent.
Keep the account owner and the reviewer separate. The account owner is the person who controls the identity; the reviewer is responsible for resolving it. An invitation sender may help explain the history without being authorised to approve continued access.
Take a dated snapshot before making changes. If the workspace cannot export records, use an approved manual inventory. Check what your workspace and current plan expose rather than assuming every status, history item, or administrative action is available.
2. Find candidates without treating similar names as proof
Look for several kinds of overlap, not just identical email addresses:
- The same person invited to a current address and a former address.
- An active account alongside a pending invitation for an alternate address.
- Two active accounts with different roles or team memberships.
- A former staff member whose name appears on both a named and a shared account.
- An account with an unfamiliar display name but an address associated with a known person.
Use name similarity, address patterns, invitation history, and the staff roster to create investigation candidates. None is sufficient on its own. Two people can share a name, and two addresses reaching the same mailbox do not necessarily represent one workspace account.
Preserve the original address in the worksheet. You can create a separate comparison field for spotting likely matches, but do not erase punctuation or address suffixes and then treat the result as confirmed identity. Address handling varies, and an apparent alias may be a separately controlled mailbox.
Confirm ownership through an established channel: the person's known work contact, their manager, or the organisation's designated mailbox administrator. Do not rely solely on a reply from the questionable address. That establishes access to that mailbox, not the responder's authority to hold workspace access.
3. Use a filled reconciliation worksheet
Fictional worked example: All people, addresses, references, dates, findings, and outcomes below are hypothetical. The worksheet illustrates a recommended review design, not an existing product control or a customer result.
In this hypothetical review, the staff roster identifies Priya Shah and Mateo Ruiz as current staff, Lena Brooks as departed, and Alex Chen as a current contractor. Each record groups related identities under one person or investigation case. The distinction between planned action and verified closure prevents a decision from being mistaken for completed removal.
Case R-01: current address plus an old-address invitation
Roster reference: STAFF-041 Person / account owner: Priya Shah Roster status: Current staff; support team Access decision owner: Support manager Reviewer: Workspace administrator Identity U-114: priya.shah@example.com Observed state: Active; support role Identity I-208: p.shah@example.com Observed state: Pending invitation; support role Investigation outcome: Manager and mailbox administrator confirm that p.shah is Priya's former address. Priya uses U-114 for current work. Authorised identity: U-114 Redundant route: Invitation I-208 Action: Cancel I-208; retain U-114 with approved support scope. Closure check: Invitation record inspected after cancellation: cancelled. Fresh pending-invitation review: no invitation for p.shah. U-114 permissions checked against manager's approval. Result: Closed; checked 14 May by a second administrator.
Case R-02: two active accounts with different permissions
Roster reference: STAFF-067 Person / account owner: Mateo Ruiz Roster status: Current staff; operations team Access decision owner: Operations manager Reviewer: Workspace administrator Identity U-130: mateo.ruiz@example.com Observed state: Active; operations role Identity U-052: m.ruiz@example.com Observed state: Active; administrator role Investigation outcome: Manager confirms both identities belong to Mateo. U-052 was used for an earlier assignment; admin access is no longer approved. An assigned work queue still names U-052. Authorised identity: U-130; operations scope only Redundant route: U-052 Action: Reassign the queue through the supported process; remove U-052 access; address existing sessions through available controls or the documented support process. Closure check: Queue responsibility accepted by the new owner. Fresh user review shows U-052 has no active membership. Authorised session check cannot open the workspace as U-052. U-130 opens the intended queue without admin permissions. Result: Closed; checked 15 May by a second administrator.
Case R-03: departed staff member with an alternate address
Roster reference: STAFF-023 Person / account owner: Lena Brooks Roster status: Departed Access decision owner: Former manager Reviewer: Workspace administrator Identity U-077: lena.brooks@example.com Observed state: Already inactive Identity U-162: lena.contract@example.com Observed state: Active; reporting role Identity I-219: l.brooks@example.com Observed state: Pending invitation Investigation outcome: Former manager confirms both active and inactive accounts were Lena's. Mailbox administrator confirms the invitation address was another address assigned to her. Authorised identity: None Redundant routes: U-162 and I-219; verify U-077 remains closed. Action: Remove U-162 access, cancel I-219, review any other memberships exposed by the available inventory. Closure check: Fresh review: no active account or pending invitation for any of the three confirmed addresses in the reviewed scope. Existing-session check for U-162 completed through the approved administrative process; workspace access denied. Result: Closed; checked 14 May by a second administrator.
Case R-04: similar name, unresolved ownership
Roster reference: CONTRACT-012 / unresolved candidate Known person: Alex Chen, current contractor Access decision owner: Contractor sponsor Reviewer: Workspace administrator Identity U-181: alex.chen@example.com Observed state: Active; limited project role Identity I-225: a.chen@example.com Observed state: Pending invitation; broader role requested Investigation outcome: Sponsor confirms U-181 belongs to the contractor but cannot identify the intended owner of I-225. Similar names are not accepted as proof that both belong to Alex. Authorised identity: U-181 only, for the approved project Unresolved route: I-225; owner not established Action: Cancel the unverified invitation under the approved access process; investigate with the invitation sender. Closure check: I-225 confirmed cancelled. No replacement invitation approved. Identity question remains open with the contractor sponsor. Next review: 16 May. Result: Invitation closed; ownership investigation still open.
These records deliberately distinguish access closure from identity resolution. An unverified invitation can be cancelled while its original purpose remains under investigation. Conversely, confirming that two accounts belong to the same person does not close the case while both remain active without approval.
4. Select the authorised identity based on work, not familiarity
For a current staff member, choose the identity associated with their approved work address and required responsibilities. Do not automatically retain whichever account was created first, used most recently, or has the broadest permissions. Those facts describe history, not entitlement.
Compare the candidate accounts' roles and memberships before choosing. One account may own work that needs reassignment while another has the correct ongoing permissions. Preserve necessary business continuity through supported reassignment or transfer processes; do not assume accounts can be merged or that deleting one preserves its history.
The permission decision should be explicit: who may use the workspace, for what purpose, and with what scope. This follows the least-privilege principle described in OWASP's authorization guidance. That guidance is a design recommendation, not evidence that a particular workspace enforces it.
Occasionally, more than one identity may have an approved purpose. Treat that as a documented exception with a named owner, a reason, distinct permissions, and a review date. Do not describe every duplicate as accidental, but do not let an unexplained duplicate become an exception by default. For a departed person, selecting an authorised identity will normally mean selecting none, subject to the organisation's approved access decisions.
5. Close invitations and active access as separate tasks
A pending invitation and an active account are different routes to review. Removing active membership does not establish that a separate invitation has been cancelled. Cancelling an invitation does not establish that an already accepted account has lost access.
- Confirm the decision. Record who approved retention, removal, or a temporary exception.
- Handle work dependencies. Identify assigned queues, responsibilities, or other ownership that must move. Use only supported processes.
- Remove redundant active access. Apply the appropriate workspace action to each confirmed account, including relevant memberships visible in scope.
- Cancel redundant invitations. Check all confirmed alternate addresses, not just the retained address.
- Address existing sessions. Determine what the removal action does to signed-in sessions. Use available session controls or seek documented support guidance when the effect is unclear.
- Record the observed result. Keep references to the changed records and the verification time, not just a note saying “done.”
For urgent removal, do not wait for a perfect ownership history before containing access that is not authorised. Follow the organisation's approved urgent-removal process, then complete the reconciliation. Avoid keeping redundant access alive solely because a routine work transfer is inconvenient; escalate the dependency to its business owner.
6. Verify the outcome from a fresh view
Reopen or refresh the administrative inventory after changes. Search by each confirmed address and account reference. Verify that retained access has the intended role, removed access has no active membership in the reviewed scope, and redundant invitations are no longer pending.
Where authorised and feasible, verify that a previously active session cannot continue to reach the workspace. Do not collect passwords or ask reviewers to impersonate staff informally. Use approved testing arrangements or administrative evidence. A login screen alone may not establish the status of an existing session.
Check the retained identity too. A removal can succeed while accidentally leaving the current staff member unable to reach their assigned work. Confirm the intended work is accessible without restoring the redundant identity or its excessive permissions.
If a check cannot be completed, record that limitation precisely. “Membership removed; existing-session behaviour not verified” is more useful than “access fully removed.” Keep the case open with an owner and next action rather than converting missing evidence into a successful result.
7. Recover safely from ambiguous or mistaken decisions
If two similar accounts turn out to belong to different people, split the worksheet case and reassess each person's access independently. Preserve the investigation trail so a later reviewer does not recombine them based on the same superficial match.
If the retained account lacks necessary work assignments, correct those assignments through the approved process. Do not immediately reactivate the old account with all its former permissions. If temporary access is necessary, document its scope, approver, and review point.
If removal was mistaken, have the decision owner approve restoration and use the supported recovery or invitation process. Record what actually changed; restoring access may not restore earlier ownership or settings. If session behaviour remains uncertain, escalate that specific question rather than repeatedly deleting and recreating accounts.
For a shared identity, identifying a nominal owner is not enough. Establish who can use it and whether continued shared use is approved. Until that is resolved, the worksheet should not claim that removing one person's named account removed all their routes.
8. Turn the first review into a measurable control
For the next review, choose one defined workspace and a roster snapshot date. Record the number of account and invitation records reviewed, unresolved owners, confirmed redundant routes, verified closures, approved exceptions, and checks still blocked. Keep those counts separate: a cancelled invitation is not a removed active account, and neither proves that every session was invalidated.
Assign every open case an owner and a next review date. Repeat the reconciliation after departures, address changes, role changes, and re-engagements, when old identities are especially relevant.
Your next action: reconcile one workspace's current users and pending invitations against the staff roster, using the filled worksheet structure above. Finish with a list of authorised identities and an evidence-backed closure status for every suspected duplicate—not merely a shorter user list.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications