---
id: KB-CO-013
url: https://app.codecontract.io/help/consigne/what-the-recipient-actually-sees
idioma: en
categoria: consigne
subcategoria: empezar
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CO-005, KB-GL-002]
citadoPor: [KB-CO-015, KB-CL-001, KB-IN-004]
---

# What the recipient actually sees

_The screen more people see than any other, described step by step._

**Responde a:** what the signer sees when opening the link · what the external portal looks like · can the supplier see other documents · what does what i send look like

For every person on your team who enters the platform there are twenty who only ever see one screen: the one the link you sent them opens. It is worth knowing what is on it, because it is the impression they take away of your company.

## What they see, in order

1. **Who is writing** — Your name and your company's, at the top. With your own branding configured, in your colours and logo.
2. **What you are asking for, as a list** — Only their part. They do not see the whole case or other participants' items.
3. **What is mandatory and what is not** — Marked. That is what lets them deliver what they have without being blocked by what they do not.
4. **A button to upload or sign** — And nothing else. No sign-up, no password, nothing to install.

## What they do NOT see

- Other participants' documents, even in the same case.
- Your internal notes or comments.
- Your other suppliers or clients.
- Anything about your organisation beyond what you asked them for.

> [!IMPORTANT]
> That separation is hard, not a setting: two subcontractors on the same case cannot see each other. It is what lets you ask them for sensitive documentation without them sharing anything.

> [!WARNING]
> Each request's title is the only thing explaining what you want. "Doc 3" leaves them guessing; the document's full name is understood first time.

> [!NOTE]
> Send yourself the link the first time you build a process. It takes a minute and changes how you write titles quite a lot.

**Does it work on a phone?**

Yes, and that is where most people open it.

**Does the link expire?**

It has a deadline; a new one can be sent immediately.

**Can they come back later?**

Yes, with the same link, and they see what they already delivered.

## Ejemplos

**A company builds its first process and sends itself the link.**

- Sees its titles read "Doc 1", "Doc 2" and "Cert"
- Rewrites them with each document's full name

→ Suppliers stop delivering the wrong document from the very first send.

**The recipient cannot tell whether the email is genuine.**

- Includes recognisable context in the notice

→ It gets opened rather than dismissed.

**The recipient cannot find the sign button.**

- Checks how it looks on a small phone

→ The path works on the real device.

**The notice text uses internal jargon.**

- Rewrites it for somebody who does not know you

→ Clarification calls drop.

**The recipient opens it and does not know what to do next.**

- Makes the next step clear on screen

→ The process completes unaided.

**Nobody on the team has ever seen that screen.**

- Sends themselves a request

→ You know what the other side sees.