We are on YouTube
There is a real benefit in allowing non-enrolled users to access teaser content within your courses. By enabling course previews, you create a bridge of curiosity that draws potential learners into the learning journey.

Remember, the course content remains securely locked until enrollment is complete. This ensures that learners are excited and fully invested in their learning experience.

Advantages:
1.) Increased Enrollment Rates: Captivating teasers spark interest, inspiring more learners to take the plunge and enroll in your course.
2.) Improved Engagement: Preview materials provide a taste of the value your course offers, making learners eager to explore the full content.
3.) Showcase Course Quality: Display your course's high standards and professionalism through meticulously designed teasers and objectives.
4.) Build Trust: Transparently displaying what learners can expect establishes trust and authenticity, enticing them to commit to their educational journey.

Here is the free plugin, called 'Restriction by course role', that you need to make this work:
https://moodle.org/plugins/availability_role

Visit us at https://flagshiplms.com/
We host Moodle sites, provide front-end administration, build Moodle courses, and answer all of your Moodle questions. 

Book a free call with us for more information.
https://calendly.com/flagshiplms/30min

Check out our artificial intelligence plugin for Moodle reports at:
https://flagshiplms.com/powerai/

There is a real benefit in allowing non-enrolled users to access teaser content within your courses. By enabling course previews, you create a bridge of curiosity that draws potential learners into the learning journey.

Remember, the course content remains securely locked until enrollment is complete. This ensures that learners are excited and fully invested in their learning experience.

Advantages:
1.) Increased Enrollment Rates: Captivating teasers spark interest, inspiring more learners to take the plunge and enroll in your course.
2.) Improved Engagement: Preview materials provide a taste of the value your course offers, making learners eager to explore the full content.
3.) Showcase Course Quality: Display your course's high standards and professionalism through meticulously designed teasers and objectives.
4.) Build Trust: Transparently displaying what learners can expect establishes trust and authenticity, enticing them to commit to their educational journey.

Here is the free plugin, called 'Restriction by course role', that you need to make this work:
https://moodle.org/plugins/availability_role

Visit us at https://flagshiplms.com/
We host Moodle sites, provide front-end administration, build Moodle courses, and answer all of your Moodle questions.

Book a free call with us for more information.
https://calendly.com/flagshiplms/30min

Check out our artificial intelligence plugin for Moodle reports at:
https://flagshiplms.com/powerai/

0 0

YouTube Video VVVVdjB0WDhNQ2FsNzNLbFpQRmd0bjFnLi1oQko3cGRRZk5z

How to Let Moodle Users Preview Course Information but Keep Course Content Locked

Flagship LMS August 26, 2023 9:02 am

Introducing PowerAI: Revolutionize Moodle Reporting with Artificial Intelligence

Flagship LMS July 21, 2023 12:53 pm

Moodle LMS administrators use a very specific set of vocabulary. For example, a "course" in Moodle has only one definition. It is the space on Moodle where teachers add activities and resources for their students. It is important that you also use this vocabulary to prevent mistakes and to streamline communication. For example, if you tell a Moodle administrator to delete a “course” when you actually mean a SCORM package, you will be very unhappy when 100% of your English 101 activities and resources suddenly disappear and your students can no longer find English 101 in their catalog.

Here are the definitions of Role and Permissions and some links where you can find more information.

Role- A role is a collection of permissions defined for the whole system that you can assign to specific users in specific contexts. The combination of roles and context define a specific user's ability to do something on any page. The most common examples are the roles of student and teacher in the context of a course.
 
This term is commonly confused with permissions. You can read more about roles here: https://docs.moodle.org/401/en/Roles_and_permissions


Permissions- These are the specific actions and abilities that define a role. They can be edited or overridden to change what a role can or cannot do. For example, normally the student role does not have the correct permission to be able to moderate a forum in a course. However, if a teacher would like to grant a user with the student role the ability to moderate a specific forum, they can override the permission for that specific context. 

This term is commonly confused with role. You can read more about permissions here: https://docs.moodle.org/401/en/Roles_and_permissions

Moodle LMS administrators use a very specific set of vocabulary. For example, a "course" in Moodle has only one definition. It is the space on Moodle where teachers add activities and resources for their students. It is important that you also use this vocabulary to prevent mistakes and to streamline communication. For example, if you tell a Moodle administrator to delete a “course” when you actually mean a SCORM package, you will be very unhappy when 100% of your English 101 activities and resources suddenly disappear and your students can no longer find English 101 in their catalog.

Here are the definitions of Role and Permissions and some links where you can find more information.

Role- A role is a collection of permissions defined for the whole system that you can assign to specific users in specific contexts. The combination of roles and context define a specific user's ability to do something on any page. The most common examples are the roles of student and teacher in the context of a course.

This term is commonly confused with permissions. You can read more about roles here: https://docs.moodle.org/401/en/Roles_and_permissions


Permissions- These are the specific actions and abilities that define a role. They can be edited or overridden to change what a role can or cannot do. For example, normally the student role does not have the correct permission to be able to moderate a forum in a course. However, if a teacher would like to grant a user with the student role the ability to moderate a specific forum, they can override the permission for that specific context.

This term is commonly confused with role. You can read more about permissions here: https://docs.moodle.org/401/en/Roles_and_permissions

4 0

YouTube Video VVVVdjB0WDhNQ2FsNzNLbFpQRmd0bjFnLkxfZlNELWNqS3JZ

Moodle Vocabulary Defined Roles and Permissions

Flagship LMS February 25, 2023 5:25 pm

Moodle LMS administrators use a very specific set of vocabulary. For example, a "course" in Moodle has only one definition. It is the space on Moodle where teachers add activities and resources for their students. It is important that you also use this vocabulary to prevent mistakes and to streamline communication. For example, if you tell a Moodle administrator to delete a “course” when you actually mean a SCORM package, you will be very unhappy when 100% of your English 101 activities and resources suddenly disappear and your students can no longer find English 101 in their catalog.

Here are the definitions of Cohort and Group and some links where you can find more information.

Cohort- A subset of users at the site or category level. The subset can be based on any profile field. For example, you can have a cohort of accountants, workers in California, trainees in a management program, new hires, people with a shoe size of 8 wide, etc. Any data that you can collect can be used to create a cohort. 

The primary purpose of cohorts is to enable all members of the cohort to be easily enrolled in a course. This can be done using Cohort sync, which, as the name suggests, synchronizes cohort membership with course enrolment. Alternatively, a cohort can be manually enrolled in a course. 

A secondary use of cohorts is to easily pull reports on specific subsets of users. Students are not aware of the cohorts in which they are members. Cohorts are only visible to users with higher level administrative permissions such as site admins, managers, and teachers. Students can belong to many cohorts at the same time.
 
This term is commonly confused with group. You can read more about cohorts here: https://docs.moodle.org/401/en/Cohorts


Group- A subset of users at the course level (context). This is used when you have groups of users (perhaps from a different school or company) taking the same course and you want to quickly see completion reports for each of those groups of users, rather than all the users in the course. Groups can also be used when you want a supervisor from the school or company to be able to check on completions for their own users but not be able to see data on other schools or companies. This term is commonly confused with cohort. You can read more about groups here: https://docs.moodle.org/401/en/Groups

Moodle LMS administrators use a very specific set of vocabulary. For example, a "course" in Moodle has only one definition. It is the space on Moodle where teachers add activities and resources for their students. It is important that you also use this vocabulary to prevent mistakes and to streamline communication. For example, if you tell a Moodle administrator to delete a “course” when you actually mean a SCORM package, you will be very unhappy when 100% of your English 101 activities and resources suddenly disappear and your students can no longer find English 101 in their catalog.

Here are the definitions of Cohort and Group and some links where you can find more information.

Cohort- A subset of users at the site or category level. The subset can be based on any profile field. For example, you can have a cohort of accountants, workers in California, trainees in a management program, new hires, people with a shoe size of 8 wide, etc. Any data that you can collect can be used to create a cohort.

The primary purpose of cohorts is to enable all members of the cohort to be easily enrolled in a course. This can be done using Cohort sync, which, as the name suggests, synchronizes cohort membership with course enrolment. Alternatively, a cohort can be manually enrolled in a course.

A secondary use of cohorts is to easily pull reports on specific subsets of users. Students are not aware of the cohorts in which they are members. Cohorts are only visible to users with higher level administrative permissions such as site admins, managers, and teachers. Students can belong to many cohorts at the same time.

This term is commonly confused with group. You can read more about cohorts here: https://docs.moodle.org/401/en/Cohorts


Group- A subset of users at the course level (context). This is used when you have groups of users (perhaps from a different school or company) taking the same course and you want to quickly see completion reports for each of those groups of users, rather than all the users in the course. Groups can also be used when you want a supervisor from the school or company to be able to check on completions for their own users but not be able to see data on other schools or companies. This term is commonly confused with cohort. You can read more about groups here: https://docs.moodle.org/401/en/Groups

5 0

YouTube Video VVVVdjB0WDhNQ2FsNzNLbFpQRmd0bjFnLno4WGYyU0p3NU1F

Moodle Vocabulary Defined: Cohort and Group

Flagship LMS February 25, 2023 4:58 pm