Purpose is to ensure more advanced use cases are still supported in new elearning platform in addition to more public use cases. Fields controlling access are now * enroll: who can enroll on course: public (everyone, simply click on join button), invite (added by already members) and payment (in bridge with website_sale, if SO with product is confirmed); * enroll_group_ids: automatically add members of those groups to the channel to ease having groups for a given subset of users; * visibility: who can see a channel and its slides: public (everyone, it means channel is visible on website for example), members (hidden for non members) * website_published on channels and slides; non publishers cannot see what is not published, whatever other parameters; * upload_group_ids: who can upload on a channel; * download_security on a slide is completely removed as it makes no sense for most slide types; To ensure a better user experience responsible of a channel is added in its members. People uploading a slide are now also allowed to read it to avoid having inconsistency behavior between upload_group_ids and access rules. Some tests are added. This commit is linked to task ID 1942836 and PR #31239. Co-Authored-By: Aurélien Warnon <awa@odoo.com> Co-Authored-By: Thibault Delavallée <tde@odoo.com>
19 lines
746 B
XML
19 lines
746 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<data noupdate="1">
|
|
<record model="slide.channel" id="channel_public">
|
|
<field name="name">Our documentation</field>
|
|
<field name="promote_strategy">most_viewed</field>
|
|
<field name="website_published" eval="True"/>
|
|
<field name="enroll">public</field>
|
|
<field name="description">Public access to presentations and documentation.</field>
|
|
</record>
|
|
|
|
<record id="slide_channel_tag_group_data_other" model="slide.channel.tag.group">
|
|
<field name="name">Tags</field>
|
|
<field name="sequence">20</field>
|
|
<field name="website_published" eval="True"/>
|
|
</record>
|
|
</data>
|
|
</odoo>
|