> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/integrations/overview/curricula-integration.md).
# Curricula Integration
Learn how to integrate Curricula with Sprinto to automate training compliance checks and sync learner activity.
The Curricula integration (Huntress, formerly Curricula) allows Sprinto to automatically sync training assignments and learner activity to automate security awareness training controls.
This integration helps enforce and monitor onboarding and periodic infosec training compliance across your organisation. Once connected, Sprinto retrieves assignment status and learner activity from Curricula to compute training-related checks.
Sprinto automates **4 controls** and **2 checks** through this integration.
***
### **Prerequisites**
Before you begin the setup:
* Log in to the **Sprinto dashboard**.
* You must have **admin access** to your Curricula (Huntress) account.
* Ensure your organisation has an active Curricula subscription.
* Ensure that pop-ups are enabled in your browser to complete the OAuth flow.
**Permissions required (via Curricula):**\
Sprinto requires the following read-only permissions:
* `account:read`
* `assignments:read`
* `assignments:learner-activity`
* `learners:read`
**Data used by Sprinto:**
* Account
* Assignment
* Learners
***
### **Steps to Connect Curricula to Sprinto**
#### **Step 1: Locate the Curricula integration**
1. Log in to your **Sprinto dashboard**.
2. Navigate to **Settings → Integrations → Available**.
3. Search for **Curricula**.
4. Click **Connect** on the Curricula integration card.
***
#### **Step 2: Review controls and permissions**
In the Connect Curricula drawer:
* Review the s**upported controls**.
* Review the **training checks**
Scroll down to review:
* Permissions required
* Data used by Sprinto
* Additional information about access type
Click **Next** to continue.
***
#### **Step 3: Start the OAuth connection**
The next drawer displays the OAuth prerequisites and setup instructions:
* Ensure you have admin access to your Curricula account.
* You will be redirected to Curricula to complete the authorisation.
Click **Connect**.
***
#### **Step 4: Log in to Curricula**
You will be redirected to the **Huntress (formerly Curricula)** login page.
1. Enter your administrator **email address** and **password**, or sign in with a supported authentication method.
2. After successful authentication, grant the required permissions requested by Sprinto.
Once authorised, Sprinto completes the integration and begins syncing data.
***
### **After Connecting Curricula**
After the connection is successful:
* Sprinto automatically imports learner data, training assignments, and completion status from Curricula.
* Training-related checks are updated automatically for onboarding and periodic requirements.
* You can track assigned and completed training within the **Compliance → Training** or **integrations detail** views of Sprinto.
If the connection fails or permissions are insufficient, return to **Settings → Integrations → Curricula** to retry or reauthorise.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sprinto.com/integrations/overview/curricula-integration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
