Understanding Activity Events
Each activity recorded by the Woolf platform contains an immutable snapshot of essential information. Once logged, this data is permanently stored and cannot be altered. These records ensure full transparency and traceability for accreditation and audit purposes.
📊 Activity Events & Triggers
The table below outlines the core activity events tracked by Woolf’s Airlock API and SDK, including how and when they are triggered:
| Event | Trigger |
|---|---|
consumeResource |
When a student consumes an accredited resource on your LMS. Automatically tracked via Airlock SDK. |
addSubmission |
When a college claims that a student submitted an assignment. Airlock SDK must sign this in real time, and actual data must be synced with AMS within 12 hours. |
addAttendance |
When a college logs student attendance for a meeting. Strong evidence is required and must be submitted within 12 hours. |
addGrade |
When a teacher submits a grade. The Airlock SDK must sign the event in real time, and grading data must be pushed to AMS within 12 hours. |
addFeedback |
When a teacher provides feedback. Must be signed by SDK in real time and synced to AMS within 12 hours. |
addCollegeStudent |
Triggered when a student is added to a college using the API or via the AMS interface. |
addDegreeStudent |
Triggered when a student is invited to a degree via API/AMS or applies to a degree program on the Woolf platform. |
addCourseStudent |
Triggered when a student consumes a course resource for the first time. Enrollment to the course is automatic. |
submitCourseGraduation |
Triggered when a compliant student is submitted for course graduation via the API or AMS interface. |
submitDegreeGraduation |
Triggered when a compliant student is submitted for degree graduation via the API or AMS interface. |
🧾 How to View Logged Activities
To fetch activity logs for a student, use the activities query in the API. This allows you to audit tracked data, including submissions, attendance, feedback, and resource consumption.
💡 Note: All events must follow real-time and actor-based principles. Exceptions (e.g., offline exams or meetings) require explicit approval from Woolf’s Accreditation Team during onboarding.