> For the complete documentation index, see [llms.txt](https://herd-security.gitbook.io/herd-security-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://herd-security.gitbook.io/herd-security-docs/campaigns/regscale-integration.md).

# RegScale Integration

File Herd's training completion and progress reports in RegScale as Evidence records, quarterly and annually, so auditors find training evidence without anyone exporting a CSV.

## Overview

If RegScale is your audit system of record, Herd can file your training evidence there. Herd creates a RegScale **Evidence** record and attaches the training completion and progress report as a CSV:

* **Quarterly progress report**: a snapshot of every training assignment, filed a day after each quarter closes.
* **Annual completion report**: the assignments made or completed during the year, filed a day after each year closes.
* **On demand**: either report for the period in progress or the last one closed, for example last year's report ahead of an audit.

Herd only **writes** to RegScale. It reads nothing back, apart from one check that your token works when you save the connection. Each report is its own Evidence record. Herd doesn't map it to controls or security plans.

***

## Before you begin

* A **RegScale service account** and its access token (in RegScale, **Settings → Service Accounts**). The service account's roles must let it create Evidence and upload files.
* In Herd, both the **Org Integrations** and **View dashboard** (`reporting.dashboard`) permissions. Saving the connection and pushing a report need both, because the report leaves Herd. Seeing the connection needs only Org Integrations.

***

## Connecting RegScale

Under **Settings → Integrations**, open the **RegScale** card (in the **Dev & Compliance** section) and expand **RegScale Connection Settings**:

* **RegScale URL**: your RegScale instance, the address you sign in to, for example `https://your-company.regscale.io`.
* **RegScale Access Token**: the service-account token. It is stored encrypted and never displayed again. To change the RegScale URL later, you enter the token again.
* **Evidence Owner ID** (optional): the RegScale user recorded as the owner of each Evidence record. Leave it blank to use the account the token belongs to.

Click **Save RegScale Configuration**. Herd checks the token against RegScale before saving. It refuses a token RegScale rejects, a URL it can't reach, and a token that expires before the next scheduled report.

A new connection doesn't go back and file periods that had already closed. The tile shows **First scheduled quarterly report** and **First scheduled annual report** so you know when the first automatic ones arrive. Use the push buttons for anything earlier.

***

## Pushing a report now

Once connected, the tile has four buttons:

* **Push this quarter (to date)**
* **Push last quarter**
* **Push this year (to date)**
* **Push last year**

Each files one Evidence record with the CSV attached. Clicking twice while a push is running doesn't file a second one.

***

## What's in the report

The CSV has the same rows as the training report export on the [Reports page](https://herd-security.gitbook.io/herd-security-docs/reports/reports.md), one per assignment, plus a **Completed By Period End** column (**Yes** or **No**) next to each assignment's current status.

* The **quarterly** report covers every assignment made by the end of the quarter.
* The **annual** report covers only that year's assignments, meaning those assigned or completed during it. It includes people who left during the year (with the assignments that were open when they left), people on leave, and trainings archived after the year began. It leaves out assignments an admin removed and trainings that were deleted.

A period ends at 12:00 UTC on the first day of the next one, so a completion on the evening of the last day, in US time zones, still counts.

***

## Status and errors

The tile shows the **RegScale URL**, when the access token expires, when Herd last pushed, the **Latest Evidence record** number, the last and next scheduled reports, and the result of the last run with its assignment row count.

If RegScale refuses the token or a report (for example, the token was revoked or the service account lost a role), the tile shows **Auto-sync paused** with the error and the time of the next automatic retry, rather than retrying every couple of hours. Fix the cause in RegScale and click **Sync now**, or push a report by hand. A successful push clears the wait. If a retry finds that the Evidence record it created earlier was deleted in RegScale, Herd files that period on a new record.

To stop, click **Disable**. Reports already in RegScale stay there, but Herd files no new ones until you reconnect.

***

## Related

* [Drata Integration](https://herd-security.gitbook.io/herd-security-docs/campaigns/drata-integration.md): a daily push of training completions and policy attestations into Drata.
* [Reports](https://herd-security.gitbook.io/herd-security-docs/reports/reports.md)
