# Access code

An access code is a short code the sender gives the signer by a separate channel, such as a phone call, that the signer must enter before the document opens.

## In plain words

A signing link sent by email proves one thing: someone could read that inbox. Most of the time that is enough. But inboxes get shared, forwarded and sometimes taken over. An access code adds a second thing the signer must know, delivered another way.

The idea is simple. The link arrives by email. The code arrives by phone, text from your own phone, or in person. Someone who only has the email can't open the document.

## An example

A recruiter sends an [offer letter](/templates/offer-letter) to a candidate's personal address, which they have never confirmed. They set an access code and read it to the candidate on their final call. The candidate opens the link, enters the code and signs. The record shows the code step was passed.

## How it shows up in docuinked

Add `access_code` to a signer when you call `create_document`. docuinked stores only a hash of it. When the signer opens their link, the page asks for the code before showing anything else. The page tells them the sender protected the document and will have shared the code directly.

```json
{"signers": [{"name": "Sam Ortiz", "email": "sam@example.com",
              "access_code": "4827"}]}
```

docuinked doesn't send the code for you. That is the point: it must travel outside email. SMS and ID checks are coming, and are not available today.

## When to use one

- The document is high value: an offer, a large sale, a lease.
- You haven't confirmed the email belongs to the signer.
- An agent prepared the document, and you want a step no agent with inbox access could pass alone.

Our [approvals page](/docs/approvals) explains that last case.

## Common confusions

**An access code is not identity proofing.** It shows the signer had information you gave them. It doesn't show who they are the way an ID document check would.

**It is not a password.** It is set per document and per signer, and the signer doesn't create an account.

**Knowledge questions are weaker.** Questions drawn from credit files are known to be weak. US federal identity guidance says they shall not be used for identity verification. A code you chose and shared yourself is a different thing.

## Related terms

- [Human-in-the-loop](/glossary/human-in-the-loop)
- [Embedded signing](/glossary/embedded-signing)
- [Notarization](/glossary/notarization)

## Sources

Checked 2026-11-07.

- [NIST SP 800-63A-4](https://pages.nist.gov/800-63-4/sp800-63a/proofing/)
- [UETA 1999 text, section 9 on attribution](https://scs.nevada.edu/wp-content/uploads/2020/07/FED_Act99.pdf)

## Common questions

### What if the signer loses the access code?

Share it again by the same outside channel. Don't email it, or the code adds nothing.

### Can each signer have a different code?

Yes. The code is set per signer, so two signers on one document can have two codes.

### Should I put the access code in the email message?

No. Anyone with the email would then have both pieces. Keep the code off every channel the link travels on.