In Knowledgeworker Share, you can specify whether posts are mandatory or optional for learners. This lets you map required training, optional further training, and information in your system. This article contains the key details.
Whether a post is mandatory or optional can be specified under "Post completion" when creating or editing the post later. Enable or disable the "Mandatory" option.

Whether a post is mandatory or optional affects several components.
Display:
Posts have a banner on their post image in the stream that identifies them as mandatory or optional. Learners can therefore see immediately whether a post is required. Posts can also be filtered in the stream by whether they are mandatory, so learners can search specifically for required training, for example.
In a curriculum, mandatory posts are marked with an exclamation mark to signal to learners that they must complete the post to complete the curriculum successfully.
Post completion:
For the "News" and "Download" post types, the way a post is completed differs between optional and mandatory posts. Optional posts are considered complete after they have been viewed for three seconds. If "Mandatory" is enabled, learners must actively confirm that they have acknowledged the information by clicking the "Read" button to complete the post.

Curriculum completion:
Whether included posts are mandatory or optional is also relevant for completing curricula. A curriculum can be completed only after all of its mandatory posts have been completed. If the curriculum sequence is also predefined, subsequent posts are unlocked only after the preceding mandatory post has been completed.

Enrolment in events:
If an event is configured as mandatory, all selected users are enrolled in it and receive the "open" status until the event is completed. If the event is optional, enrolments are initially created with the "offered" status. The enrolment status changes to "open" only when users confirm their attendance.

Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article

