> For the complete documentation index, see [llms.txt](https://docs.yansalabs.com/okta-orchestrator/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yansalabs.com/okta-orchestrator/technical-docs/attestation-tracking.md).

# Attestation Tracking

**Attestation** tracking allows you to monitor who has requested access to particular [**Access Entities**](/okta-orchestrator/technical-docs/access-provisioning/access-entities.md), the status of that access, and when/if that access will be recertified or removed.

Attestations provide a granular view of a user's lifecycle with an Access Entity. Auditing and automatically recertifying access using Attestations is crucial to monitoring user access in an organization and ensuring that costly license entitlements are appropriately allotted.

{% hint style="info" %}
Attestations are configured on each [**Access Entity**](/okta-orchestrator/technical-docs/access-provisioning/access-entities.md) record. All active and expired Attestations can always be viewed at **Okta Orchestrator -> Attestation -> Attestations** in the left nav.
{% endhint %}

<figure><img src="/files/EKvTsN5CzYYQqoJQ5AjW" alt=""><figcaption><p>Attestation</p></figcaption></figure>

* **Access entity**: [**Access Entity**](/okta-orchestrator/technical-docs/access-provisioning/access-entities.md) to which the Attestation is associated
* **Assigned to**: User who requested access
* **State**: Current status of the Attestation
* **Recertification date**: Date on which the Attestation was (or will be) recertified
* **Forced expiration**: When enabled, no recertification of the attestation is possible - access will be automatically revoked on the Recertification date
* **Parent**: This is either the initial request (RITM) that spawned the Attestation, or the previous Attestation that has spawned a renewal