---
id: KB-ET-017
url: https://app.codecontract.io/help/your-workspace/when-someone-has-two-accounts
idioma: en
categoria: espacio-de-trabajo
subcategoria: usuarios
audiencia: administrador
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-ET-011, KB-AD-015]
citadoPor: [KB-ET-016]
---

# When someone has two accounts

_The same person logging in with two different emails: why it happens and why to fix it early._

**Responde a:** a user has two accounts · i logged in with another email and see nothing · merging duplicate accounts · changing a user's email

It is a small mess that grows: someone logs in one day with their personal email because an invitation landed there, and another day with the company one. To the platform they are two different people, and from then on everything splits in two: what they see, what they have done, and what reaches them.

## How you notice

| Symptom | What is happening |
| --- | --- |
| "I log in and cannot see my things" | They are in the other account's session |
| "I do not get the alerts" | They go to the other email |
| They appear twice in the user list | There are two accounts, not a display glitch |
| The log attributes actions to two names | Which complicates any later review |

> [!IMPORTANT]
> The fourth row is the most annoying long term and the one nobody sees coming. If the same person has worked six months with two accounts, the history is split: answering "who did this" requires knowing those two identities were one person, and only whoever was there at the time knows that.

## How to fix it

1. **Decide which one is the good one** — Nearly always the company domain: it outlives the person and fits domain-based access.
2. **Move access to that one** — With the same permissions they had on the other, no more.
3. **Withdraw the other, without deleting its history** — What they did stays; what is removed is the ability to keep using it.
4. **And tell them which to use** — That is half the problem: without knowing, they will log in wherever the password is saved.

> [!WARNING]
> Mind the order: if you withdraw the old account first and that person had tasks, alerts or files in their name, those are left ownerless and nobody notices until something expires. Reassign first, withdraw after — exactly as with a leaver.

## How to prevent it

**En corto**

- Always invite the corporate email, even if the person asks for their own.
- Enable domain-based access if your team shares a domain.
- And review the user list occasionally: duplicates are visible at a glance.

> [!NOTE]
> The external collaborator who works with several companies is a different case: there it is normal to use one email with access to several organisations. That is not two accounts, it is one account with several accesses, and it works as it should.

**Can the two accounts be merged?**

What moves is the access; each one's history stays where it was generated.

**Do they take two seats?**

While both are active, yes. Another reason to resolve it early.

**What if the good email changes because the domain changes?**

Access is updated; no new account is needed.

## Ejemplos

**An employee sometimes logs in with her personal email and sometimes with the company one.**

- They reassign her tasks to the corporate account before withdrawing the other
- They confirm which one she should use

→ She stops missing alerts and the log attributes her work to one person again.

**One person has two accounts and works from both.**

- Merges into one and removes the other

→ The history stops splitting.

**Files are spread across their two accounts.**

- Reassigns everything to the account being kept

→ Nothing is left orphaned.

**Notices go to the account they do not use.**

- Updates the address on the files

→ Notices arrive where they get read.

**An extra licence is consumed.**

- Removes the duplicate account

→ The account reflects the real people.

**An account is deleted and its actions vanish from the history.**

- Deactivates rather than deletes

→ The record of what they did is kept.