---
schema_version: "1"
id: 05337bb72651a113023cf428bce167bb5725cc655ff2c8ea3a89decc813dd35a
title: Create Evidence Requests for IT Compliance
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/it_srvcs_create_evidence_request.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.it_srvcs_create_evidence_request.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7fafef18a18bd7be70838fadc1a97c40914a43e6b62bbd173e3224e6ef5fd595
description: Create compliance evidence requests to gather artifacts from subject matter experts for an audit. Each request specifies what evidence is needed, who should fulfill it, and when it's due. Requests can be created manually or autogenerated from an audit template.
products:
  - Service Cloud
  - Agentforce IT Service
release: "264"
---
# Create Evidence Requests for IT Compliance

Create compliance evidence requests to gather artifacts from subject matter experts for an audit. Each request specifies what evidence is needed, who should fulfill it, and when it's due. Requests can be created manually or autogenerated from an audit template.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> Editions with Agentforce IT Service.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d77964e74">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d77964e74 ">To create evidence requests:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d77964e74 ">Compliance Admin permission set</td>

          </tr>
        </tbody>
      </table>

An evidence request represents a specific piece of evidence that's needed to satisfy an audit control or requirement—such as a system configuration export, a user access review report, or a policy acknowledgment screenshot. Requests are assigned to the subject matter expert or team who owns the relevant system or process, and they move through a defined lifecycle from creation to fulfillment to verification.

You can start a request from one of the out-of-the-box sample requests by cloning it, or create one from scratch when no sample fits.

1. From App Launcher, open the **Evidence Hub** app.
    
    The Evidence Hub is a separate, restricted workspace from the IT Compliance app. Only users assigned an Evidence Management permission set can access it.
2. Go to the **Compliance Evidence Requests** tab.
3. Create the request.
    
    - To start from scratch, click **New**.
    - To start from a sample, open a **\[SAMPLE\]** request that fits your audit, click **Clone**, and edit the cloned record.
4. Fill in the evidence request details:
    
    - Title. A descriptive name that tells the fulfiller exactly what evidence is being requested, like **End-to-End Offboarding SLA Report (Access Revocation)**.
    - Type. The kind of artifact you expect back. Choose **Documentation** for policies and reports, **Inquiry** for written attestations, **Observation** for walkthroughs and screenshots, **Configuration** for system settings exports, or **Implementation Details** for procedure write-ups.
    - Compliance Audit. The parent audit this request rolls up to. Linking the request makes it visible on the audit's Evidence tab and ties it to the audit's scope and timeline.
    - Assignee. The SME or fulfiller responsible for providing the evidence. Notifications are sent to this user when configured.
    - Requested By. The compliance officer or audit program manager who owns the request.
    - Priority. **High**, **Normal**, or **Low**. Use this to help fulfillers triage their queue.
    - Due Date. The date the evidence is needed by. The due date drives the SLA timer and milestone tracking on the request.
    - Instruction. A clear, specific ask. State the expected evidence, the systems it should come from, and any acceptance criteria the fulfiller needs to meet.
    - Observation Statement. Optional. Use this field to capture findings or notes for the fulfiller as the request progresses, like a missing piece of evidence the assignee still needs to provide.
5. Save the record.
    
    The request is created with status **Draft** and an auto-generated request number (for example, **CER-000000009**).

![Example: requesting evidence for an offboarding SLA audit](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-it_service-264-0-0-production-enus/0a574a10-4c7a-4681-aacf-0767f8beaad4/images/icon_example.png)

Example: requesting evidence for an offboarding SLA audit

Suppose your team is running an internal governance audit for least privilege verification, and you need proof that access for terminated employees is revoked within the 24-hour SLA. You create a single evidence request that the assignee can fulfill with artifacts from multiple source systems:

- Title: End-to-End Offboarding SLA Report (Access Revocation)
- Type: Implementation Details
- Compliance Audit: \[SAMPLE\] Internal Governance Audit for Least Privilege Verification
- Assignee: Rachel Anderson, IT Compliance Analyst
- Requested By: Audit Program Manager
- Priority: Normal
- Due Date: 4/30/2026
- Instruction: Provide evidence that access to all systems is being revoked within 24 hours of an employee's termination. Expected evidence: official termination date from HRIS, IT offboarding ticket from the ticketing system, suspended user status from the identity provider, and verification from Data Workspaces that all non-SSO local accounts were disabled.

The assignee can now fulfill the request by uploading evidence artifacts from the Evidence Hub or, for employees who don't have a Salesforce license, from the IT Service employee portal. Once every artifact has been verified, mark the request as accepted to close out this phase of the audit.