Dates & Release Conditions

Release conditions empower NICC instructors to create custom learning paths tailored to their unique courses, students, and modalities. Instead of relying on the manual “Hide from Users” buttons, incorporating Start and End dates and Release Conditions can allow for automated and intuitive access. If you set a Start, End, or Due date for an assessment, a reminder will helpfully appear on your students’ Upcoming Events page and the Agenda view in the Calendar tool.

Dates

    1. DIID recommends the use of Start Dates to automate and control student access whenever appropriate.

    2. Due Dates can be used to ensure clarity of instructional expectations.

      • Note that the use of Due Dates without a corresponding End Date means late work is accepted by default, but helpfully arrives flagged as late.

      • Users will be able to helpfully see the title and description of items before the Start Date and after the End Date, but will not be able to access the content item.

    3. Instructors who allow late work should avoid the use of End Dates, since this setting will have to be manually adjusted to allow any student to submit an assignment after the End Date.

    4. Some activities include extra options that allow instructions to make the activity visible but restrict access for the learner to post or submit until a prescribed date. Learn more about this on the discussion and assignment pages.

    5. We recommend viewing your course homepage and course calendar via the 'More Tools' menu from the learner view to see what appears in the course calendar. You can make adjustments to what appears there in the 'Manage Dates' tool in the 'Course Admin' menu.

Release Conditions

    1. Selecting Add Dates & Restrictions on any Brightspace Content Item allows instructors access to Release Conditions, or conditionally restrict student access to the item beyond basic calendar criteria.

      • Note that release conditions totally hide a content item from students until the corresponding criteria are met.

    2. Release conditions are highly customizable

      • Students could be required to view (click on) a specific content topic before gaining access to a quiz,

      • Students could be required to post (or reply) to a discussion topic before they could access the next course module, etc.

      • Release conditions can also be added to intelligent agents to create email notifications for users.