> 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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.yansalabs.com/okta-orchestrator/technical-docs/attestation-tracking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.