---
id: KB-CL-003
url: https://app.codecontract.io/help/collaboration/what-you-have-signed-for-others
idioma: en
categoria: colaboracion
subcategoria: externos
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CO-005, KB-CL-001]
citadoPor: [KB-CL-011]
enLaApp: https://app.codecontract.io/participaciones
---

# What you have signed or delivered to others

_Your own history when someone else is the one asking, not you._

**Responde a:** where do i see what i have signed · documents i delivered to other companies · history of my signatures · find a document i signed a while ago

Almost the entire help centre is written from the requester's side. But if you have an account and are also somebody's supplier, you are on the other side too: you sign contracts, deliver certificates, answer requests. All of that is your history as well.

## Why having it together helps

**En corto**

- Finding what you signed with a client two years ago, without asking them.
- Seeing what someone is waiting on from you right now.
- Knowing which of your documents are out there, and since when.

## What people look for here

| Situation | What is sought |
| --- | --- |
| A client disputes an old agreement | The exact document signed, with its date |
| Documentation has to be renewed with several clients | What was delivered to each and when |
| Someone asks whether something was sent | The receipt, rather than memory |

> [!IMPORTANT]
> What you signed is signed by you and cannot be modified afterwards, exactly like what others sign for you. It is the same property seen from the other side, and worth bearing in mind before signing: what you accept stays accepted.

> [!NOTE]
> If you are both client and supplier to the same company, this shows half the relationship and your own cases show the other. They are two views of one deal.

> [!WARNING]
> Having an account does not mean you need one to respond to somebody. Your own suppliers do not need one, and it is better not to ask them for one.

**Can I download what I signed?**

Yes, with its evidence inside.

**Does my team see it?**

Depending on the permissions you have set.

**Can a document I signed be verified?**

Yes, on the public page, like anyone else's.

## Ejemplos

**A company needs an agreement it signed with a client three years ago and no longer has the email.**

- Looks it up in its own participation history

→ Retrieves it with its evidence without asking the client, who is precisely who they are arguing with.

**A client asks for copies of everything signed over two years and it has to be hunted across four inboxes.**

- Checks the history of what was signed and delivered to that client
- Checks which version of each document they received
- Delivers from the platform so there is a record

→ The handover is prepared in an afternoon and it is on record exactly what they received and when.

**A different version from the one signed is handed over.**

- Checks which version carried the signature

→ Both parties hold the same document.

**The client says they never received something that was sent.**

- Checks the send and delivery dates

→ The dispute closes on the record.

**A search by file name returns nothing.**

- Searches by content or by client

→ It is found without depending on what it was called.

**Nobody knows what has been delivered to each client.**

- Checks the history per client

→ The picture exists without reconstructing it.

**A document is resent and the second delivery is not recorded.**

- Records each send with its date

→ The history reflects every occasion.

**The client asks for the copy years after the relationship ended.**

- Retains the history per the retention policy

→ The request is met without depending on a lost folder.
