After completing this video, viewers will understand how to lock and unlock class content by adjusting login and payment requirements. They will learn how to make classes accessible only to logged-in users, and optionally require payment for access. The video demonstrates how to easily update these settings for any class using a straightforward interface. By the end, users will be able to control who can view or participate in class content based on their login and payment status.
Following are the key things you will be able to do after you watch this demo:
Locking and Unlocking Content Overview 0:10
Josh Lomelino explains the purpose of the demo, which is to demonstrate how to lock and unlock content.
He mentions that content can be hidden or made accessible only to logged-in users, with additional conditions like requiring payment.
The process involves managing access at the class level, where each class contains units, content items, and resources.
Josh emphasizes that the class itself needs to be modified to control access to its content.
Modifying Class Settings for Access Control 1:05
Josh demonstrates how to modify a class, using the example of the coding Academy.
He sets "login required" to true to mandate that users must log in to access the class.
Josh explains the option to specify whether payment is required, either as a one-time payment or a recurring subscription.
He clarifies that if payment is not required, users can log in but do not need to pay, making the class free but still requiring a login.
Handling Payment and Access Permissions 1:57
Josh discusses the settings for blocking users without active payment.
If payment is not required, he sets this option to false to allow free access to logged-in users.
For paid classes, he sets this option to true to ensure that users must have an active payment to access the content.
He explains that the system checks if the payment is up to date, especially for recurring payments within the subscription period.
Finalizing and Applying Access Settings 2:31
Josh concludes by explaining that once the changes are applied and submitted, users will need to adhere to the new access settings.
He reiterates that these settings control whether a login is required and if payment is necessary.
The process allows for managing various access permutations through a simple user interface.
Josh emphasizes that these settings will be enforced when users attempt to access any content within the modified class.