Skip to main content

Importing audit requests as an External Auditor

Roles and permissions

The following roles can import requests into an audit:

  • Administrators

  • Compliance managers

  • Users who are members of an audit can import requests

  • External auditors who are members of an audit can import requests

External auditors can't create an audit but can import requests into an existing audit where they are members. If you need to create an audit, contact an administrator or compliance manager in the organization where you need to create the audit.

Note

If your request list contains references to controls or labels, check with an administrator to ensure that the controls and labels are already created in Hyperproof and that the IDs you are using match those in Hyperproof.

Step One: Downloading the example CSV

  1. From the left menu, select Audits.

  2. Select the audit where you want to import requests.

  3. Select the Requests tab for the audit.

  4. Click the Import link.

    The Import requests window opens.

  5. Click Download the example CSV.

Step Two: Editing the CSV

Replace the contents of the example CSV with your own requests. Be sure to follow the format of the example file, as well as the instructions on the page, to ensure that your requests can be successfully imported.

Note

The CSV must contain ALL headings listed below even if they are optional. Keep in mind that headings are case-sensitive!

Heading

ID

Should contain an ID that's unique to your organization. Leave the field empty if this is a new request. This field is required.

Reference

A field to store an auditor-provided request reference. This is an optional field.

Summary

A field to concisely describe what work needs to be done to fulfill the request. This field is required.

Assignee

Must be formatted as FirstName LastName (email address), i.e. Jennifer Cook (jcook@lunabtechnologies.org). This is an optional field.

Tip: If no assignee is provided, the request is assigned to the individual who imports the CSV.

Additional tip: The assignee's email address must match the email address they use to sign in to Hyperproof.

Status

A field for tracking the status of the issue. This is an optional field.

Tip: Hyperproof recognizes the following request statuses: Not started, In progress, Internal review, Submitted to auditor, Needs revision, Closed, and Approved.

Due date

The date the request needs to be completed. This is an optional field.

Note

Dates on imported records are parsed based on the date formats associated with your locale. If no valid date can be determined, Hyperproof displays an error. See Data interpreted by browser locale for a list of supported locales.

Description

This is the full definition of the request. It can be a multi-line string. This is an optional field.

Linked controls

A field for control IDs linked to the request, e.g. ETSI422-4.2.4. This is an optional field.

Tip: If linking multiple controls IDs to a request, enter the control IDs in a comma-separated format, i.e. CC3.1.1, CC3.2.5, CC3.3.4.

Linked labels

A field for labels linked to the request, e.g. Code of Ethics. This is an optional field.

Linked programs

A field for programs linked to the request, e.g. Luna B.'s ETSI Program. This is an optional field.

Linked audits

A field for audits linked to the request, e.g. Quarterly Audit 2023. This is an optional field.

Linked registers

A field for registers linked to the request. Values are Risk and Vendor. This is an optional field.

Linked risks

A field for risk IDs linked to the request, e.g. R-AC-2. This is an optional field.

Linked vendors

A field for vendors linked to the request, e.g. Galactacore. This is an optional field.

Custom fields

 

Below is a snippet of a sample import file.

example-csv-requests.png

Step Three: Importing the CSV

After you’ve made the necessary changes to the CSV, it can be imported into Hyperproof.

  1. Drag and drop the CSV file into the Upload CSV File field, or click Select file to upload to upload it manually.

  2. Click Import.

    Hyperproof checks the CSV to ensure that there are no errors. You’ll be alerted if Hyperproof encounters any errors.

  3. If Hyperproof didn’t detect any errors, click Next. If Hyperproof detected errors, do one or both of the following:

    1. First, use the Error viewer to identify the errors. Second, correct the errors directly in the CSV. This ensures that the CSV is up-to-date should you need to re-import in the future.

      Tip

      Use the forward and backward arrows to cycle through the errors. The Error viewer gives specific information on what needs to be corrected.

       

    2. Remove rows that contain errors by clicking Remove all rows with errors. Note that this doesn't remove any data in the actual CSV.

  4. Click Next.

    The CSV is imported.

In this section: