Inside the course platform
Decide who can enter a course and which modules they can reach. Keep learner progress and assessment results here. Removing enrollment affects this access path.
Keep your lessons for the learners they were created for. Encrypt e-learning videos and manage playback with learner passwords, device binding, and watermarks.

Protecting an e-learning library means protecting more than the page where a lesson appears. A video may be watched in an LMS, downloaded for study, or supplied in a USB training kit. Build protection around those delivery paths so your lessons reach the right learners without becoming an unrestricted collection of files.
Use enrollment rules to control entry, secure the actual video delivery, and require authorization for protected files learners receive. GiliSoft Video DRM Protection encrypts video packages and adds Playback Passwords, device binding, learner watermarks, expiration, and configured online password revocation. Keep assessments and course progress in your learning platform.
Start with what the learner receives, not just the name of the course platform. A private course page, a video URL, and a protected lesson package each control a different point in the learning journey.
| Learning delivery | Protection to apply | Release decision |
|---|---|---|
| Lessons watched in the course website | Learner sign-in plus the video host's private playback controls | Confirm that the media itself requires access, not only the surrounding page. |
| Video files downloaded for study | GiliSoft protected packages with individual playback rules | Deliver protected output and the intended player, not the open master MP4. |
| USB training or field-learning kits | Protected packages with the chosen PC or USB binding | Choose whether access follows an approved computer or the issued USB device. |
| A blended course with web and local lessons | Apply the appropriate protection to each path | Keep a delivery list so the same lesson is not also exposed as an unrestricted download. |
For browser delivery, a host can require expiring signed tokens, as documented in Cloudflare's private playback controls. Encrypted browser playback can use a licensing system such as Widevine. These are video-host controls; GiliSoft's protected-file workflow does not automatically reconfigure an existing web player.
Your learning platform remains the place for enrollment, prerequisites, module visibility, quizzes, and completion. For example, Moodle access restrictions can use dates, grades, groups, and activity completion to determine when content becomes available.
Decide who can enter a course and which modules they can reach. Keep learner progress and assessment results here. Removing enrollment affects this access path.
Decide which credential or device can play the delivered content, what watermark appears, and when access expires. A password already issued to a learner needs its own access record.
Link the two through a clear administration process. Do not assume a website enrollment change automatically issues, renews, or revokes a GiliSoft credential. For the individual learner lifecycle, use the online course video access guide.
A learner forwards the downloaded MP4, not the course-page link. Supply protected output so the next viewer still needs valid playback authorization.
One fixed class password can travel with the files. Use device-bound credentials when access should belong to an approved learner device.
Use a learner-specific visible watermark and available capture restrictions. Keep the enrollment-to-password record so an identifiable watermark can be investigated.
Label deliveries by course and edition. Keep the published package, project settings, and credential records together so updates and access changes refer to the right release.
Use GiliSoft on Windows to prepare the protected video delivery. Common source formats include MP4, AVI, WMV, MPG, RM, RMVB, FLV, and VOB. The three settings below connect the content group, learner identity, and playback period; follow the complete DRM setup guide for every export step.
Add the lessons for one delivery group. Save the Project ID and Encryption Key with the course and edition record, then choose the output and password mode. For an approved Windows computer, use the PC Binding workflow. For a USB-bound delivery, select the corresponding USB binding option rather than just copying the file onto a drive.
In Advanced Settings > Basic Settings, choose a fixed or floating watermark, font, color, spacing, and movement frequency. Keep it readable without obscuring a demonstration or captions. This screen defines the style; the learner's text is entered when creating their Playback Password.
If you need to cancel leaked or withdrawn access later, configure online blacklist verification before export. Do not enable an internet-blocking playback rule that conflicts with the verification your plan requires.
After reviewing the binding, watermark, and verification settings, create the protected output. Choose GEM or EXE according to the edition and intended playback environment. Keep the open source videos and publisher key out of the learner delivery.
For Windows PC Binding, collect the approved computer's Machine Code and use it with the matching Encryption Key in Create Play Password. Set the learner's Text Watermark and explicit Expiration Date where needed. Record the issued password against the course and learner.
A play-count limit or disabled seeking is optional. Allow enough replay for revision, language support, and accessibility; a restricted player does not replace an assessment or prove lesson completion.
Keep previews separate from the paid library. Use learner credentials for protected downloads and a clear access period. Link learners to one consistent player and activation guide.
Separate confidential modules by audience and edition. Keep staff or partner access records with the issued credentials, while your LMS handles training assignments and completion reporting.
Use the platform for prerequisites and examinations. Set a specific end date on file-based lesson access when required, without treating a play counter as certification evidence.
Choose the intended PC or USB binding and test playback with the expected connectivity. Set realistic renewal and cancellation procedures for learners who work away from the network.
For an individual student's second computer, renewal, or refund, see course access changes. For packaging and handing over the files, see protected course download delivery.
A hidden page helps organize access, but it is not protection for an MP4 already saved by a learner. A password-protected ZIP secures the archive; once extracted, an ordinary video can still be forwarded. A school logo identifies the brand, not the individual learner who shared a recording.
Use each measure for its actual purpose: platform access for entry, encrypted playback for delivered files, device binding for approved devices, and learner-specific watermarks for traceability. None makes every possible screen recording impossible.
Publish a short protected sample to a small test group before releasing the library. Test the same package, player, device types, and network conditions learners will use.
| Test | Expected outcome |
|---|---|
| Enrolled learner on the approved device | The lesson opens with sound and the intended watermark; navigation and captions remain usable. |
| The same PC-bound password on a different computer | That credential does not authorize the other computer merely because the package was copied. |
| Private modules or a newer edition | The learner receives only the intended protected delivery; no alternate open master is exposed. |
| An expired test credential | The approved device follows the configured expiry and verification rules. |
| A password added to the configured online blacklist | First confirm valid playback on its approved device, then confirm rejection after the online list is checked. A wrong-device failure alone does not prove revocation. |
| Travel or interrupted connectivity | The chosen verification setup behaves as planned. Learners know when an online check or support contact is needed. |
Deliver the protected lessons, the intended player, opening instructions, and a support route. State the supported learner devices clearly. Keep transcripts or accessible alternatives available, and keep unprotected masters and publisher records outside the learner bundle.
Match protection to delivery. Use your learning platform for enrollment and course availability, the video host's security controls for browser playback, and protected packages when learners receive video files. GiliSoft Video DRM Protection adds playback passwords, device binding, watermarks, expiration, and configured online password revocation to protected file delivery.
Enrollment controls who can reach a course page or download link. It does not, by itself, stop a learner forwarding an ordinary MP4 after downloading it. For lessons supplied as files, deliver protected output and require playback authorization instead of relying only on the private course page.
No. Keep enrollment, prerequisites, assessments, grades, and completion reporting in your learning platform. Use GiliSoft for protected video playback. A play-count limit is not evidence that a learner watched or understood a lesson, and automatic synchronization with an LMS requires a specifically implemented integration.
The protection applies to the video content inside the package, not to the physical act of copying the package file. With device-bound playback, another device still needs valid authorization to view that content. A class-wide fixed password can be shared and should not be described as individual device control.
Yes. Choose the product's USB binding workflow for content that should be associated with an approved USB delivery device. Simply saving a protected file on a USB drive does not enable USB binding. Test the intended drive and the behavior of a copy moved away from it before distributing the training kit.
Use the LMS to control module visibility and release conditions. For file delivery, create separate protected packages and access records for groups of lessons with different permissions. Do not put all modules in one shared-access package and assume an LMS prerequisite also restricts the local copy.
An online blacklist takes effect when the configured player checks the updated list, so it cannot instantly reach a learner who stays disconnected. Configure blacklist verification before exporting when later cancellation is required. Use an explicit expiration date for planned access periods and test the selected verification method in the intended offline environment.
Create protected output on Windows and select the supported GiliSoft player and package combination for the learner's platform. Playback can be delivered across supported Windows, macOS, iOS, and Android scenarios, but a Windows EXE does not run on a phone and the Windows Machine Code procedure is not a universal mobile activation process.
No. Available capture restrictions can deter supported software recording paths, but they cannot guarantee every recorder is blocked or stop an external camera filming a screen. Combine access controls with a readable learner-specific watermark and a practical response process for leaked credentials.
Prepare a sample lesson with GiliSoft Video DRM Protection and verify the learner experience before releasing the full course.