---
id: KB-AD-003
url: https://app.codecontract.io/help/administration/removing-someone-from-the-team
idioma: en
categoria: administracion
audiencia: administrador
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-AD-002, KB-ET-002, KB-AD-020]
citadoPor: [KB-TZ-003, KB-ET-010, KB-ET-013, KB-AD-002, KB-ET-007, KB-CF-007]
enLaApp: https://app.codecontract.io/settings/members
---

# Removing someone

_What happens to their work, their pending signatures and their documents._

**Responde a:** delete a user from the team · an employee is leaving what about their account · transfer someone's cases · revoke a colleague's access

Someone is leaving. The urgent thing is to cut their access; the important thing is that their work is not orphaned. They are two different jobs and both are worth doing.

1. **Remove access today** — The same day, not at month end. Their open account is no longer watched by anyone.
2. **Hand over what they were carrying** — Their open cases and pending sends move to someone else. Otherwise they sit waiting for a person who is not coming back.
3. **Leave their trail alone** — What they did stays signed by them, with their name and date. It is not rewritten.

## What goes and what stays

| Item | What happens |
| --- | --- |
| Documents they uploaded | Stay. They belong to the organisation, not to them |
| Cases they owned | Transferred to whoever you say |
| What they signed | Stays signed by them, permanently |
| Their personal account data | Deleted on request, without erasing the record |

> [!NOTE]
> Signatures staying in their name is not an oversight: a signature that changed owner when someone left would prove nothing.

> [!WARNING]
> If that person was the only administrator, appoint another before removing them. Otherwise the organisation is left with nobody able to change anything.

**Can I restore the account if they come back?**

You invite them again. A new account with their history intact.

**What about half-finished signature requests?**

They are reassigned to the new owner without redoing the whole circuit.

**Are the third parties they dealt with notified?**

Not automatically. If they held a live relationship, it is worth saying so.

## Ejemplos

**The purchasing manager leaves with eleven supplier onboardings open.**

- Access is removed on their last day
- The eleven cases move to their replacement
- Their earlier signatures stay in their name

→ No supplier is left waiting on an address nobody reads any more.

**Somebody leaves and their access stays active.**

- Revokes access on their last day

→ The account reflects who works here.

**Their account is deleted and their actions vanish.**

- Deactivates rather than deletes

→ The history stays true.

**Their files stay in their name.**

- Reassigns them before the departure

→ No third party is left waiting.

**Notices keep going to their address.**

- Changes the recipient on the files

→ Notices reach somebody who exists.

**Closing their open sessions is forgotten.**

- Closes the sessions on deactivation

→ Access is genuinely cut.