---
id: KB-TZ-005
url: https://app.codecontract.io/help/traceability-and-compliance/what-gets-recorded-about-what-i-do
idioma: en
categoria: trazabilidad
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-TZ-002, KB-GL-014, KB-TZ-020]
citadoPor: [KB-TZ-007, KB-TZ-009, KB-TZ-010]
---

# What gets recorded

_Everything that touches a document leaves a trail, and that works in your favour._

**Responde a:** which actions are recorded · is it stored who opens a document · is there a log of what i do · am i being monitored on the platform

Almost everything that happens around a document is recorded: who uploaded it, who opened it, who approved it, who downloaded it and when. It sounds like surveillance and it is not: it is what makes it possible to answer questions that would otherwise be one person's word against another's.

## What is recorded

| Moment | What is kept |
| --- | --- |
| Upload | Who and when |
| Send | To whom, on which channel, whether it arrived and whether it was opened |
| Approval or rejection | Who decided, when and with what reason |
| Download or view | Who accessed it and when |
| Change to a value | The old value, the new one and who changed it |

## What it is for, in practice

- Closing a "you never told us" with a date rather than an argument.
- Showing an auditor that the control was genuinely applied, not merely written down.
- Knowing who can answer a question about a two-year-old case.

> [!IMPORTANT]
> The log cannot be edited, not even by an administrator. That is what gives it value: a log someone could retouch would prove nothing, because whoever would retouch it is precisely who has the motive.

> [!WARNING]
> Recording who downloads what also protects you: if one day a document leaves where it should not, the question has an answer.

> [!NOTE]
> None of this has to be switched on: it exists from day one. The only decision is how long it is kept, which follows your policy.

**Can anyone erase their trail?**

No.

**Can everyone see the log?**

No, only administrators. It is sensitive information about people on the team.

**Is a third party's activity recorded?**

Yes: when they opened their link, what they delivered and when they signed.

## Ejemplos

**Nobody remembers who approved a certificate that turned out to be expired.**

- The case log is checked

→ It shows who approved it and when; the criterion is fixed instead of blame being guessed at.

**Nobody knows what is recorded for each action.**

- Checks the log of a real case

→ You know what you have.

**Something is asserted that the log does not support.**

- Checks first what is on record

→ You assert what can be demonstrated.

**A client asks what is stored about their activity.**

- Explains which fields make up the log

→ The answer is specific and verifiable.

**A specific action is hunted in the history.**

- Filters by date, user or file

→ It is found without walking the whole thing.

**There is concern the log could be altered.**

- Verifies that entries cannot be edited

→ The value lies in nobody being able to correct it.