Skip to main content

The Guardian

Monitor your platform and protect it from content theft and account sharing.

B
Written by Blanca Berger

What Is Guardian For?

With Guardian, you can detect suspicious activity by your members and protect your LearningSuite from account sharing and content theft.

Guardian automatically monitors various activities and informs you as soon as a member displays suspicious behavior. Depending on your settings, it can also take action automatically.

This keeps you in control of your platform and lets you decide how suspicious members should be handled.

How Does It Detect Suspicious Users?

Guardian continuously checks how your members use the platform and looks for two types of irregularities: account sharing and content theft.

Account Sharing

Guardian counts the number of devices a member is logged in to at the same time.

If a member exceeds the device limit you set, this may indicate that multiple people are using the same account. You define what happens in this case during setup.

Content Theft

To detect whether content is being automatically scraped or downloaded, Guardian looks for several signals, for example:

  • An unusually high number of requests within one minute

  • A very high number of page views within a few minutes

  • An unusually high number of courses in a short period of time

  • Accessing transcripts without playing the associated video

  • Accessing videos outside your platform, for example through download extensions

  • Suspicious browser identifiers, such as those used by bots and scripts

In addition, certain pages contain a hidden export called a honeypot. It is not visible to people and therefore cannot be accessed by a regular user. If this export is accessed, it is a clear indication that a bot or an AI tool is scraping the page.

Severity Levels

Each detected irregularity is assigned one of three severity levels. This determines how Guardian responds automatically.

  • Low: Individual, weak signals, such as many courses in a short period of time. This is often harmless, for example when a member is reviewing everything before an exam.

  • Medium: A clear pattern, such as too many requests per minute or transcripts without video playback. This may indicate content theft.

  • High: Clear indications, such as a bot program or the hidden export. A clear sign of automated access.

If several medium irregularities occur in one day, Guardian evaluates them together as a high irregularity.

You define how Guardian should respond to each severity level during setup.


Set Up Guardian

When you open Guardian for the first time, you will be guided through the setup.

Here, you can define which activities should be monitored and how Guardian should respond to irregularities.

1. Account Sharing: Set the Device Limit

In the first step, you can define how many devices a member can be logged in to at the same time.

You can also decide what happens when this limit is reached or exceeded.

You have three options:

  • Allow login anyway: The member can continue logging in. You will be notified of the irregularity in Guardian.

  • Old device must be logged out: The member must first log out of one of their currently logged-in devices before they can use a new device.

  • Limit device changes: You can limit the number of device changes per rolling year. Once this limit is reached, the member can no longer log in with new devices.

2. Content Theft: Automatic Responses

Here, you define how Guardian should respond to suspicious activities.

You can define different actions depending on the severity of the irregularity.

You have four options for each of the three severity levels (see above):

  • Ignore: The activity is saved in the history but is not marked as a suspicious case.

  • Suspicious case: The activity is marked as a suspicious case. Your team members can view and review the case in Guardian.

  • Quarantine until clarification: The member is temporarily placed in quarantine and must explain why the irregularity occurred. Once the clarification has been submitted, they can use LearningSuite again.

  • Quarantine until review: The member is placed in quarantine and can only use LearningSuite again after a team member has reviewed and approved the case.

3. Message Templates

Under “Message Templates,” you can define which messages your members receive automatically.

These messages are displayed, for example, when a member must provide a clarification or is blocked.

You can edit the templates at any time and customize the message directly before requesting a clarification or blocking a member.

4. Who Is Guardian Active For?

Here, you can define which members should be monitored by Guardian.

You also have the option to limit monitoring to specific groups or Bundles.

This lets you decide which members the protective measures should apply to.

5. Summary

In the final step, you will receive an overview of your selected settings.

Here, you can review your configuration once more before activating Guardian.


The Guardian Dashboard

The Guardian Dashboard provides an overview of all current irregularities on your platform.

You can see at a glance which members are currently in quarantine and which new suspicious cases have been detected.

In addition, the “Recent Actions” section at the bottom shows what your team has recently done in Guardian, such as who resolved a case, granted access to a member, or left a note. This keeps everyone up to date, even with multiple team members.


Quarantine and Suspicious Cases

Guardian distinguishes between suspicious cases and members in quarantine.

Quarantine

Members in quarantine cannot use LearningSuite normally on a temporary basis until their case has been resolved.

A member can be placed in quarantine in two ways:

  • Automatically: Depending on the severity level of the irregularity, Guardian automatically places a member in quarantine if you have configured this in the settings.

  • Manually: A team member requests a clarification in a suspicious case.

When the member is placed in quarantine, they must provide a clarification and explain how the irregularity occurred. Depending on the settings, the member is then granted access again immediately or must wait until a team member has reviewed and approved the clarification.

Suspicious Cases

This section displays members for whom suspicious activity has been detected.

Your team members can review these cases and decide whether further action is necessary.


Case Handling

When you open a suspicious case or a member in quarantine, you receive a detailed overview of the affected member.

The overview is divided into three sections:

  • History: A timeline of everything that happened in this case: detected irregularities, Actions taken by your team members (such as calls, notes, or requests for clarification), and the member’s responses.

  • Irregularities: All suspicious activities Guardian detected for this member, including severity level and details, such as the number of requests or the browser used.

  • Devices: The devices the member is currently logged in to and how many device changes they have remaining. Here, you can log out individual devices or grant the member additional device changes.

This gives you all important information in one place and helps you assess the case.


What Actions Can You Take?

As a team member, you have several options for handling a case.

Ignore Case

You can ignore an irregularity if you consider it harmless.

This closes the current case. If the member becomes suspicious again, they will reappear in Guardian.

Log a Call

If you have spoken to the affected member by phone, you can document the call.

This allows other team members to understand what was discussed.

Leave an Internal Note

You can leave internal notes in the case history.

This is especially helpful when multiple team members are handling cases together and want to document important information.

Disable Guardian

With this option, you can disable monitoring for a specific member.

This is useful, for example, for test accounts or trusted individuals.

You can then find members for whom Guardian has been disabled under the “Whitelist” tab.

Block Member

If you determine that a member is violating your rules, you can block them.

You decide whether the block is permanent or applies until a specific date. For a temporary block, the member is automatically granted access again when it expires.

The member receives a message in which you can explain the reason for the block.

Review Clarifications and Grant Members Access

When a member is automatically placed in quarantine, they must provide a clarification.

In this clarification, the member can explain why the suspicious activities occurred.

As soon as a clarification is available, you have additional Actions available as a team member:

  • Request another clarification: If the explanation is insufficient, you can ask the member to provide further information.

  • Grant member access: If the case is resolved for you, you can grant the member access again.

When granting access, you also have the option to require confirmation from the member.

This allows you to ensure that the member confirms certain notices or conditions before they can use the platform normally again.


Resolved Cases

Under “Resolved,” you can find all completed cases: cases you ignored and members whose clarification was accepted.

For each case, you can see when and by whom it was completed, as well as the related internal note. If a member was granted access with a message, you can also see whether they have already confirmed the message.

You can reopen a resolved case at any time if new evidence emerges and block the member afterward if necessary.


Blocked Users

Under “Blocked Users,” you can find all members blocked by a team member.

You can see when the block began, when it expires (for temporary blocks), and which irregularity was most recently detected.

Use “Unblock” to remove the block. The member will then have the same access as before the block.


Whitelist

Under the “Whitelist” tab, you can find all members for whom Guardian has been disabled.

These members are no longer monitored by Guardian.

This is especially useful for test accounts or members you intentionally want to exclude from monitoring.

You can reactivate Guardian for any member on the Whitelist at any time and see what the last irregularity was before they were added to the Whitelist.


Additional Settings

In addition to the settings you define during the initial setup, you have further options available.

Access Grant Templates

Under “Access Grant Templates,” you can prepare messages to use when granting members access.

You can select these templates directly when granting access.

This means you do not have to write a new message every time and can ensure that your members receive consistent information.

Notice Pop-up for Members

You can display a notice Pop-up to your members that informs them that their activities on the platform are being reviewed.

This allows you to communicate transparently that you use measures to protect your content.


If you have any questions, please contact our support team through the HelpCenter in the bottom-left corner. We usually respond within 5 minutes on business days from 09:00 to 17:00.

Did this answer your question?