> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/evaluate-requirements/attach-evidence.md).

# Attach Evidence

Provide requested evidence to support requirement validation.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Attach Evidence

<i class="fa-user">:user:</i> **Performed By:** Assigned Resource

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

***

## Accessing the Task <a href="#accessing-the-task" id="accessing-the-task"></a>

The **Attach Evidence** task can be accessed through any of the following:

* The **To Do** module.
* The **Notification Panel** (via the **Notification Bell**).
* The **direct link** provided in the email notification.

***

## Completing the Task

After receiving an evidence request, review the details and provide the requested information.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

{% hint style="success" %}
For guidance on common form features and functions, see [**Working with Forms**](/interfacing-help-files/end-users/exploring-apps/working-with-forms.md).
{% endhint %}

{% hint style="info" %}

#### Saving Your Work

To save progress without submitting, click **Save** in the top-right corner of the panel.

* The task remains in the **To Do** module for you to revisit and complete later.
  {% endhint %}

***

{% stepper %}
{% step %}

### Provide Evidence

Use the available options to provide the requested evidence.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

#### <i class="fa-upload">:upload:</i> Upload Files

Use the **Attach Evidence** field to upload supporting documents or files relevant to the request.

#### <i class="fa-link-simple">:link-simple:</i> Add Evidence Links

You can also provide evidence using URLs:

* **Input URL to the Evidence:** Enter the web address for the resource.
  * Expected Format: `http://example.com`
* **URL Display Name:** Enter a user-friendly name.
  * If left blank, the URL is used as the display name.
* **Add Evidence Link:** Click to add the link.
  * As links are added, they populate the below grid.

    * To remove a link, select the corresponding **Delete** ( <i class="fa-trash-can">:trash-can:</i> ) icon.

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Confirm deletion by clicking <strong>Save Changes</strong> or clicking outside the grid. To cancel, click <strong>Discard Changes</strong> or <strong>Undo</strong> ( <i class="fa-rotate-left">:rotate-left:</i> ).</p></div>

***

{% endstep %}

{% step %}

### Provide Response

Include a response to the evidence request to provide context, clarification, or additional details.

<p align="center"><kbd><strong>IMAGE</strong></kbd><br></p>

***

{% endstep %}

{% step %}

### Submit Evidence

From the **Task Resolution** dropdown, select **Send**, then click **Submit**.

{% hint style="info" %}

#### What Happens Next

Once submitted, the requested evidence is integrated into the [**Validate Requirement**](/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/evaluate-requirements.md#validate-requirement) form based on its type: files appear in the **Attach Evidence** field, while links are added to the **List of Links** grid.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

Additionally, an overview of the evidence exchange is presented in the **Evidence Repository** grid.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>
{% endhint %}

***

{% endstep %}
{% endstepper %}

***


---

# 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://interfacing.gitbook.io/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/evaluate-requirements/attach-evidence.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.