Learning Record Store (sysadmin)
TABLE OF CONTENTS
- 1 Introduction
- 2 Before you start
- 3 Activate and configure the LRS
- 4 Manage data retention
- 5 Manage third-party access
- 6 View or download LRS records
- 7 What data appears in the report
- 8 Security, audit logging and fair use
- 9 Troubleshooting
1 Introduction
The itslearning Learning Record Store (LRS) is a secure system for collecting, storing and managing learner activity and outcome data. It uses the xAPI structure to record learning events as statements, so that selected learning data can be stored centrally and made available for approved reporting or analytics use.
Customer administrators can activate or deactivate the LRS, define which user profiles are included, configure data retention, manage third-party access and view or download filtered LRS records.
The LRS is built around the open, standards-based xAPI data format, with near real-time data collection and storage of learning outcome data. Access for external systems, including AI-driven tools, is controlled by the customer through the third-party access settings described in section 5.
If a school connects an external system to the LRS, examples of the kind of analysis it could support include:
- Identifying frequently accessed courses and resources, to inform content development.
- Building adaptive learning paths.
- Detecting patterns that may indicate learner disengagement or underperformance.
- Generating personalised feedback based on a learner's submissions and interactions.
- Linking resource usage to learner outcomes, to help refine content.
Note: itslearning does not use LRS data in its own features or reports. Any use of this data, including by AI-driven systems, takes place only through third-party access that the customer has explicitly configured (see section 5).
Prerequisite: The LRS is an optional add-on. In Germany, it is enabled by default for all customers. In other markets, the LRS add-on must be enabled for the site by itslearning Support before customer administrators can activate it and start collecting data. Contact your itslearning representative if you would like to enable this feature.
1.1 What the LRS stores
The LRS stores learning activity and outcome data from supported learning events. The data is stored in a standards-based format and can be used for reporting, analytics and controlled export to approved third parties.
Each LRS statement follows the xAPI structure Actor > Verb > Object. A statement also includes context information, such as school and course information, and a timestamp in UTC.
Note: For example, a statement could record that: a learner [Actor] received a score [Verb: "ReceivedScore"] of 9 out of 10 [Result] for the assignment "Essay about photosynthesis" [Object], in a specific course and school [context], on a specific date and time in UTC [Timestamp].
The timestamp records when the interaction took place. The LRS stores one timestamp per interaction and does not track time spent.
The LRS follows a data minimisation approach. It is intended to store relevant learning data only and limit the time window to a maximum of 5 years for individual statements. Learners' names are not stored in the LRS; it operates by identifiers only. If names are needed, you should allow your partner to enrich data using other sources and match users by the synchronisation key.
2 Before you start
| Requirement | Details |
|---|---|
| LRS add-on | The add-on must be enabled by itslearning Support at customer request. |
| Access | The user must have permission to manage the LRS. Permission is given by enabling the profile setting Manage Learning Record Store. See section 3 for details. |
| Included users | Data is collected only for profiles where LRS data collection is enabled. |
| Administration path | Go to Admin > Logs and Services > Manage Learning Record Store |

3 Activate and configure the LRS
Activating the LRS starts data collection for the selected user profiles. Deactivating it stops new data collection and starts a deletion grace period.
Admin setting: If your sysadmin profile does not already have LRS management enabled, go to Administration > Profiles > System Administrator and enable Manage settings for learning-objective reports. Remember to click Save at the bottom of the page.

3.1 Select which profiles are included
Administrators decide which user profiles are included in the LRS using site profile settings.
- Go to Admin > Profiles.
- Open the profile that should be included in LRS data collection.
- Enable Collect Learning Record Store data.

- Save the profile.
- Repeat the steps for each profile that should be included.
Note: LRS data collection is generally enabled for student profiles only. If a user has a teacher profile but is enrolled as a student in a course, their data is not collected unless the teacher profile also has LRS activated.
3.2 Start collecting data
- Go to Admin > Logs and Services > LRS management.
- Click Start collecting data.
- Confirm the activation.

After activation, learning activity data begins feeding into the LRS for the selected profiles. Data retention policies start applying to stored data, and third-party access can be configured.
3.3 Stop collecting data
Important: Deactivating the LRS is a destructive action. No new data is collected, third-party access is revoked, and all LRS records are permanently deleted after the grace period if the LRS is not reactivated.
- Go to Admin > Logs and Services > LRS management.
- Use the LRS activation control to disable the LRS.

- Read the confirmation dialog.
- Type disable to confirm, or Cancel to keep the LRS active.

When the LRS is disabled:
- No new data is collected.
- A 7-day grace period starts. During the grace period, third-party data requests return empty responses, and existing records remain if the LRS is reactivated, with a gap in data covering the deactivated period.
- Third-party credentials are revoked after one week.

- If the LRS is not reactivated within the grace period, all LRS data is permanently deleted after one week.
4 Manage data retention
The LRS uses separate retention periods for assessment data and engagement data. By default, itslearning uses the maximum retention time. The retention period is selected from a drop-down list, in increments of one year: 1–5 years for assessment data, and 1–2 years for engagement data.
| Data type | Minimum retention | Maximum retention | Default | Description |
|---|---|---|---|---|
| Assessment data | 1 year | 5 years | 5 years | Scores and assessment-related records. |
| Engagement data | 1 year | 2 years | 2 years | Navigational or usage events, such as page or course visits. |
After the defined retention period, data is securely deleted from the itslearning Learning Record Store.

Important: When a user is permanently removed from itslearning, their data is also deleted from the LRS. This deletion is irreversible by the sysadmin. Recovery from backup may be possible through itslearning Support, but this could incur additional charges.
5 Manage third-party access
Customer administrators control which approved third parties can access LRS data. Access can be limited to all organisations or selected organisations.
Partners have read-only access to the LRS data using the xAPI compliant API. They do not have a user interface to the LRS. For details, see the developer documentation.
5.1 Register new partner
- Go to Admin > Logs and Services > LRS management.
- Open the third-party access area.

- Add or register the third-party organisation.
- Add the contact person details, including name, email address and phone number where required.
- Add comments if needed.
- On save, a new page opens with the partner details.

5.2 Grant partner access to data
Before a partner can access LRS data, you need to:
- Select whether they have access to all or selected organisations on your site.
- Share the client ID with the partner.
- Send an email to the partner so that they can create their client secret.
Partners and their current access rights are summarised in a table on the LRS management page. To view partner details and manage their client secrets, click on their name in the list.

| Partner status | Details |
|---|---|
| Active | Partner has created a client secret and can read data from the LRS. |
| Revoked | Partner's client secret has been revoked and they cannot read data from the LRS. |
| Pending | An email with a link to generate a client secret has been sent to the partner, but they have not yet created it. |
| Expired | An email to generate a client secret has been sent to the partner, but the link expired before the client secret was created. |
| Draft | The partner was registered, but the email with the link to generate a client secret has not yet been sent. |
5.2.1 Manage organisation access
Go to Manage organisation access to define the data access scope for the partner. You can select whether they have access to all data on your site or to selected organisations only.

Changes to the data access scope take effect immediately.
5.2.2 Share client credentials with partner
The client ID is created automatically when the partner is registered. Copy the client ID and share it with your partner separately.
The client secret is created by the partner using a one-time password generation link sent by email. The link expires after 24 hours.

Note: To generate the client secret, the partner must enter their client ID. Share the client ID separately before the partner uses the link to generate their client secret.
Client secrets are not stored in itslearning. If your partner has misplaced their client secret, revoke the old secret and send them a link to generate a new one.
Each partner can have two secrets active at the same time, to allow rotating the secrets. We recommend revoking old secrets periodically so that only one secret is active.

5.3 Revoke partner access to data
Administrators can revoke third-party access by removing access to organisations, revoking client secrets or deleting the partner.

Changes to third-party access take effect immediately.

6 View or download LRS records
The data in the LRS is not used for analysis or reporting in itslearning. Its primary purpose is to collect and provide near real-time access to learner interactions in an internationally recognised standard format, for analysis in external systems.
For the purpose of allowing administrators to verify that the LRS is functioning as expected, a simplified report view of the collected statements is provided.
The LRS report lets administrators filter, view and download LRS records. A download can be exported as a CSV file compressed in a ZIP file.
Note: The maximum download size is 1 million rows. If more rows match the selected filters, refine the filters before downloading.
6.1 Supported filters
| Filter | Required | Details |
|---|---|---|
| Start date | Yes | Start of the data collection period. |
| End date | Yes | End of the data collection period. |
| Organisation | No | Select one or more organisations. This is the user's home organisation. Large sites may contain hundreds of schools, so search by organisation name. |
| User | No | Select one or more users by searching for their first or last name. The search matches against itslearning's user records to find the matching person ID, which the LRS query then uses to retrieve that user's data. Note that the viewable data does not include users' names, as names are not stored in the LRS. |
| Object type | No | Filter by supported object type, such as Course, Plan, LMS Resource, Assignment, Test, SCORM, H5P or specific LTI tool. |
6.2 Search and view records
- Go to Admin > Reports > Learning Record Store report.

- Open the LRS report.
- Select the required Start date and End date.
- Add optional filters if needed.
- Click Search.
- If results are within the supported limit (max. 1 million rows), the first 100 are listed. Use Show 100 more rows to load more rows when this option is available.
- Use the download option to get all results in one file.

6.3 Download a report
- Apply the filters you need.
- Click Search.
- Check that the number of matching rows is within the 1 million row limit.
- Click Download.
- Wait until the ZIP file is prepared. When it is ready, a notification appears.
| Situation | What happens |
|---|---|
| You stayed on the page | The file downloads automatically. |
| Automatic download does not start | Click the file link to download it. |
| You left the page while the file was being prepared | The download link remains available on the page for 24 hours. |
Note: Only one download can be in progress at a time. Wait for the current download to finish, or cancel it, before starting a new one.
6.4 Report messages
| Message or state | Meaning |
|---|---|
| {0} results match your filters | The search has found {0} matching rows. |
| Too many results | More than 1 million rows match the filters. Refine the filters before viewing or downloading. |
| Preparing your LRS report. You'll be notified when it's ready. | The system is generating the ZIP file. |
| Your LRS report is ready. [download link] | The file is ready to download. |
| Something went wrong while generating the LRS report. Please try again. | The report could not be generated. Try again. This is a generic message for unknown errors, such as a lost internet connection or a temporary connection issue with the LRS. |
7 What data appears in the report
The report shows a simplified view of LRS statements. The available data depends on the filters used and the events collected for the selected period.
7.1 Report columns
| Column | Description |
|---|---|
| Timestamp UTC | Time of the recorded event in UTC. |
| User | System identifier of the learner or user who performed the action. Consists of the external sync key, hierarchy ID in itslearning, and user ID in itslearning. The user's name is not stored in the LRS. |
| Organisation | The user's home organisation. The friendly name is shown in the report view and the download, but is not stored in the LRS. |
| Verb | The action that occurred (xAPI format, in English). |
| Object type | The type of learning object (in English). |
| Object name | The name of the learning object. |
| Course name | The course connected to the event. |
7.2 Event categories
The table below is a reference of all recorded event types, grouped by category.
| Category | Examples of recorded events |
|---|---|
| Engagement events | Login, access course, plan or topic, complete plan. |
| Assignment | Viewed, worked on, submitted, completed, received score, received feedback. |
| Test | Viewed, attempted, received score, received feedback. |
| Task | Viewed, completed, received score, received feedback. |
| H5P player | Viewed, completed and received score (if shared by the H5P object). |
| SCORM player | Viewed, completed and received score (if shared by the SCORM object). |
| LTI tool | Viewed, completed and received score (if shared by the LTI tool). |
| Discussion | Viewed, interacted. |
| Survey | Viewed, completed. |
| Registration | Viewed, worked on, completed. |
| Resource extension | Viewed. |
8 Security, audit logging and fair use
The LRS follows itslearning's ISO27001 certified security framework. Communication is encrypted in transit, personal data is encrypted at rest, and all third-party access to data is controlled by the customer.
Only users with LRS management permission can view LRS data in itslearning.
Note: If access to LRS management is given to users who are not administrators at site level, they will not be able to change settings that affect all organisations, grant partner access to data outside the scope of their own organisation, or view LRS data from organisations other than their own.
The following actions are logged internally with the system ID of the user who performed the action and a timestamp:
- Activating or deactivating LRS data collection.
- Changing data retention time.
- Granting or revoking third-party access.
- Downloading LRS data.
Note: Audit logs are not available through the itslearning user interface. If needed for investigation, itslearning support can, on request, share audit logs with the customer's named support contact.
The LRS API applies fair-use protection to maintain performance and system stability by enforcing client-specific rate limits. Over-limit API requests by partners may return errors, such as HTTP 429 (too many requests in a given time), and unusual activity may lead to temporary suspension.
9 Troubleshooting
| Problem | Symptom | Solution |
|---|---|---|
| The LRS management page is not available. | You cannot find LRS management in Admin. | Check that the LRS add-on has been enabled for the site and that your profile has permission to manage the LRS. |
| No data appears after activation. | The report has no records. | Check that the relevant profiles are included in LRS data collection. Data is collected only after the LRS is enabled and for included profiles. On first activation, there is a delay of about 1 hour before data is shown in the report due to caching. |
| Too many rows match the filters. | You see the message "Too many results". | Refine the date range, organisation, learner identifier or object type filters. The limit is 1 million rows. |
| A report cannot be generated. | You see the message "Something went wrong while generating the LRS report. Please try again." | Try generating the report again. Refine the filters if the report contains a large number of rows. |
More help resources
Have more questions? Please start by asking your school administrator.
Product release notes
Stay updated with itslearning's latest releases: https://itslearning.com/product-updates
Service status
Check the current status of itslearning services: https://status.itslearning.com/
Ideas portal
Share your ideas and help shape the future of itslearning: https://ideas.itslearning.com/
Roadmap
Check out our roadmap: https://itslearning.com/global/roadmap/
The features shown are part of the project within the framework of the German Development Project (GDP), a cooperation between four German states and itslearning with the aim of improving digital education in Germany through tailor-made product developments.
Learn more about the GDP roadmap and what other features you can expect.
For German readers: more information about the project within the framework of the German Development Project.