Requests tab within an audit
The Requests tab in an audit is essential because it's where you can manage the requests for your audit. In this area, we can link controls and labels and add proof to requests.
Note: To collaborate with your auditor in Hyperproof, you'll want to add them and assign them the External Auditor role.
Note: You can now add attachments directly to a request.
The tutorial below is shown from the perspective of the administrator role with object permissions as a manager in Hyperproof. If you are in a different role in Hyperproof or have a different permission level, you may not have access to some of the areas shown, or they may be grayed out.
In this video tutorial, we'll click into this request area to view/edit and add items to the requests in this audit. We'll also discuss how you can leverage this area if you choose to collaborate with your auditor in Hyperproof.
Click the arrow to read the steps or watch the video tutorial
Linking proof to a request manually
Linking proof to a request manually
From the left menu, select Audits.
Select your audit.
Select the Requests tab.
Select the request you want to link proof to.
In the right pane, scroll to Proof.
Add your proof in one of the following ways:
Drag and drop files onto the proof grid.
Click Add proof and select one of the following:
My Computer - To use proof stored on your computer, click My Computer in the upper-left corner.
Cloud storage integration - To use proof stored in an integration, such as Drive, select the integration’s icon from the Add integration section in the bottom-left corner. Optionally, turn on LiveSync to automatically keep your proof up to date.
Paste a link - Select this option to use a website URL as proof. The URL is rendered as a “Link” file type in Hyperproof; the only information shown in the file is the URL.
Paste an image - Select this option to use a screenshot as proof. Take a screenshot (Cmd-Shift-5 on Mac, Shift-S on Windows), copy it to the clipboard, and then paste it in Hyperproof. Chrome users may need to allow this functionality if prompted by the browser (refresh the page after clicking Allow).
Existing proof - To reuse proof that already exists in your organization, select either Labels, Proof, My Controls, Vendors, Risks, or Programs from the left menu.
Linking proof to a request from a label
Linking proof to a request from a label
From the left menu, select Audits.
Select your audit.
Select the Requests tab.
Select the request you want to link proof to.
Click Link label.
Select the checkbox next to the label you want to link.
Click Confirm.
The label is linked to the request.
Requests within work items
Requests from your audit can also be found in the Requests area within Work Items. As an administrator, you can see all of the requests from each audit you've joined. If you aren't on an audit, you can navigate to the audits area and join that audit. This also makes it easier to assign requests from different audits to different users who need to work on them.
In this area, you can filter and also rearrange columns to organize the requests accordingly. You can also group select the requests to export, archive, change the status or due date, set the priority, assignee, etc.
To ensure consistency and alignment with other work items (tasks, repeating tasks, evaluations, and issues), there are some changes to the fields on requests as follows.
Click the arrow to read more below.
ID
ID
As with issues and evaluations, ID is now an auto-generated field that’s unique within an organization. The pattern for the IDs is R-N, where N is a sequential number. All existing requests (active and archived) in an organization will get a unique ID starting with the oldest request as R-1.
Why the change? Per user feedback, requests will eventually be able to show up in more than one audit. To make this possible, requests require unique IDs that can be referenced from each audit.
ID renamed to reference
ID renamed to reference
To support the new auto-generated ID field, the existing ID field was renamed to Reference, preserving existing values. Like before, Reference allows customers to capture audit references provided by an auditor.
Example: A request on a SOC2 audit might have a reference of CC1.1, which references what requirement the request is made against.
Description renamed to summary, notes to description
Description renamed to summary, notes to description
To present all work items in a unified listing, this update renames some fields to create a common set of fields across work item types. The Description field is renamed to Summary, and Notes is renamed to Description. This aligns with how most users have been using these fields.