On the other hand, Terms & Conditions should outline the rules and guidelines that learners should respect in order to use the learning platform (e.g. not uploading informal learning assets related to specific subjects). Terms & Conditions should primarily focus on Coach & Share and E-Commerce, so learners know which rules to follow when asking questions to Experts, uploading informal learning assets, writing comments on assets, and purchasing courses or learning plans in the platform.
Checkboxes with links to both sets of content appear in the login or registration form, or just after logging into the platform, for those that had already accepted an older version of either one. Learners will also find a link to the Terms & Conditions in their shopping carts and on the Share Content page in their platforms.
In the Header Message section, add an introductory message that appears above all of your policy and sub-policy text on the registration form for learners. Please note that this text can be no longer than 500 characters, and should serve as a brief introduction to what users will accept below the message in the form. Please note that this message is not mandatory, but suggested.
Then, provide a title message (this is the acceptance message that your users will see) and the text body of the policy.
In the text body, you can format and stylize the text as desired. Additionally, you can add PDF files into the body of the text by pressing the Attach Files button in the text formatting bar. Note that your platform does not track whether learners click on the link to the file or download the file, but the Versioning functionality in your platform ensures that the version of the file that is served to the end user is always the right historical one.
Creating and Managing Sub-Policies
Then, insert the sub-policy acceptance message into the corresponding text field and flag whether it’s mandatory or not. If you set a sub-policy to be mandatory, users will not be able to access their platforms until they’ve accepted the sub-policy.
Please note that when you’re creating or editing a policy in the platform’s default language, the default language fields are mandatory. However, when adding content in a language that is not the default language, the fields are not mandatory. Therefore, if you do not populate a field in one of the additional languages, that field will appear to users in the default language instead of appearing blank.
Versions are at global language level. If you update a policy in any language, a new version is created for all languages. Users will have to re-accept the policy, regardless of their platform language. Therefore, if you’re managing a policy that is published in multiple languages, you should update any necessary fields in ALL languages before pressing Save Changes and creating a new version.
In the Versioning tab of a policy, use the sliding bar in the area at the top of the page to see all of the available versions and switch between which version you want to view. For each currently viewed version, you will see the version name, who published that version and the date and time of publication.
Note on the Text Editor
Please note the text editor embedded in the platform is Froala, refer to the Froala Knowledge Base for further information on its usage. Also remember that the rendering of the output of WYSIWYG editors may be slightly different from the input, depending on the CSS rules applied.