> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fawcos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Consent and attestations

> How a farmer's consent becomes a signed attestation.

A consent names four things: **who** receives the data (your organisation), **why** (a purpose),
**what** (a scope from a fixed list) and **until when** (an expiry).

## Allowed scope items

`levels`, `tier`, `verified_area`, `crops`, `seasons`, `open_flags`, `name`, `phone`,
`nin_last4`, `parcel_geometry`.

There is no blanket consent. You receive only the items the farmer agreed to.

## Lifecycle

The consent and attestation endpoints are released next (see the [Changelog](/changelog)). This is
how they work.

1. You request consent for a purpose and scope.
2. The farmer confirms with a one-time code or their PIN, in their language.
3. FaWCOS issues a signed attestation addressed to your organisation.
4. If the farmer revokes consent, or it expires, the attestation is revoked. Check status
   before relying on one.

Every read of an attestation is logged against the farmer's consent.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.