---
id: KB-GL-001
url: https://app.codecontract.io/help/glossary/glossary-of-terms
idioma: en
categoria: glosario
audiencia: usuario
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-PS-002, KB-TL-001, KB-ET-002]
citadoPor: [KB-GL-015, KB-PS-004, KB-GL-002]
---

# Glossary: what each word means

_The terms used across the platform, each explained in a single line._

**Responde a:** what is a case in code contract · difference between a schema and a process · what is an external participant · glossary of platform terms · what does certified evidence mean

Almost every confusion in the first days is about vocabulary, not about how things work. These are the words worth getting straight, in the order you tend to meet them.

## How information is organised

**Folder** — A container for tidiness. It nests and it is optional.

**Project** — The unit of work. It does not nest, it belongs to one module, and every document lives inside one.

**Document** — The file itself: what people send you, what gets signed, or what you certify.

**Data** — The fields taken from a document: amount, date, number. Automatic reading proposes them and you confirm.

## Trackline

**Schema or process** — The template: what is asked for, in what order and from whom. Designed once.

**Case** — One specific run of a schema. One per supplier, client or matter.

**Phase** — A block of requests that go out together. The next opens when the previous is complete.

**Request** — Each thing you ask for: a document, some data, or both together.

## People

**User** — Someone in your organisation, with an account and a password. Uses a licence.

**External participant** — Someone outside — supplier, client, signer. Opens a link, has no account, uses no licence.

**Contact** — A person's record in your address book, with their email, mobile and language.

## Consigne

**Simple signature** — The signer draws their signature. When and from where is recorded.

**Advanced signature** — The same, plus confirming a code sent to their mobile by SMS.

**Evidence chain** — The full account of a signature: who, when, how and from where.

**Timestamp** — The independent certification of when it was signed, which stops the date being arguable.

## SmartCheck and traceability

**Evidence** — Something certified: a file or some data, sealed with a demonstrable date.

**Fingerprint** — The unique summary of a file. It changes completely if one character is altered, which is how tampering is detected.

**Public verification** — The page where anyone can check a document without an account and without your permission.

**Audit dossier** — The export of a whole folder with its evidence and dates.

## Platform

**Credits** — The unit used to pay for actions with an external cost: AI reading, SMS, sealing.

**Organisation** — Your company inside the platform. Each one's data is kept separate.

**Audit log** — The immutable history of who did what and when.

**Error code** — The identifier shaped E-YYMMDD-XXXX shown when something fails. It lets support find the exact problem.

## Ejemplos

**Someone new to the team tries to create accounts for suppliers as users and runs out of licences.**

- Reads the difference between a user and an external participant
- Discovers the supplier needs no account
- Cancels the invitations and runs the process with links instead

→ The licences are free again and the suppliers deliver just the same, registering for nothing.

**Two departments use «file» to mean different things.**

- Settle the vocabulary with the glossary

→ Meetings stop starting by clarifying terms.

**An internal email mentions «batch» and nobody knows if it means purchasing or production.**

- Checks the definition before replying

→ The answer addresses what was actually asked.

**A newcomer does not understand the difference between phase and file.**

- Reads the two entries in sequence

→ They start working without needing a training session.

**A supplier asks what a term in the notice means.**

- Links them the specific glossary entry

→ The clarification is a line rather than a phone call.

**An internal procedure is written using invented terms.**

- Uses the same names as the platform

→ The procedure and the tool say the same thing.