> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/audits/evidences/glossary.md).

# Glossary

This glossary defines key terms used across the **Evidences** section in Sprinto to help you better understand terminology related to uploading, reviewing, and managing audit artefacts.

<table><thead><tr><th width="185.35546875">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Evidence</strong></td><td>A file or link that proves a security control or audit requirement has been met. It can be collected automatically, uploaded manually, or generated through workflows or policies.</td></tr><tr><td><strong>Automated Evidence</strong></td><td>Evidence collected by Sprinto’s system via integrations and monitoring. It is read-only and cannot be edited.</td></tr><tr><td><strong>Workflow Evidence</strong></td><td>Evidence generated through checks run on connected platforms like AWS, Google Workspace, or GitHub. This type is also read-only.</td></tr><tr><td><strong>Evidence Requested</strong></td><td>Evidence submitted by users in response to a request created through the Sprinto dashboard. It can be uploaded, reviewed, and archived.</td></tr><tr><td><strong>Uploaded Evidence</strong></td><td>Manually added evidence files or links. This is the most flexible evidence type and supports metadata, control mapping, version history, and archiving.</td></tr><tr><td><strong>Policy Evidence</strong></td><td>Evidence automatically generated when a policy is uploaded, approved, or published in Sprinto. It is read-only.</td></tr><tr><td><strong>Evidence Group</strong></td><td>A label or category used to logically group related evidences (e.g. by audit event, department, or framework).</td></tr><tr><td><strong>Evidence Identifier</strong></td><td>A unique, auto-generated code (e.g. <em>EVD-001</em>) assigned to each uploaded evidence file.</td></tr><tr><td><strong>Evidence Collected Date</strong></td><td>The date the evidence was originally generated or obtained. This can be edited manually.</td></tr><tr><td><strong>Custom Fields</strong></td><td>User-defined metadata fields (e.g. Department, Expiry Date, Type) that help organise and filter evidences.</td></tr><tr><td><strong>Version History</strong></td><td>A log of all updates made to a given evidence item, showing previous versions and timestamps.</td></tr><tr><td><strong>Review Required</strong></td><td>A setting that, when enabled, allows a reviewer to approve or request changes to an evidence file.</td></tr><tr><td><strong>Archived Evidence</strong></td><td>Evidence that has been removed from audit visibility but remains linked to controls. It cannot be edited or updated.</td></tr><tr><td><strong>Associated Controls</strong></td><td>The specific security or compliance controls that an evidence item is mapped to.</td></tr><tr><td><strong>Audit Requirement</strong></td><td>A specific checklist item in an audit that requires proof of compliance, often fulfilled by attaching evidence.</td></tr></tbody></table>


---

# 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.sprinto.com/audits/evidences/glossary.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.