Further, course and item permissions can be used to carry through said templates, which means you can not only make sure the content is placed and consistent on every syllabus, but you can prevent certain users from taking liberties with it. That said, it might be helpful if you review any articles related to item permissions, group permissions, and even user permissions before you attempt to create complex linked template hierarchies.
To begin, you should have already created at least one template (e.g. an institutional template) because if you want to link that template to another, you must clone that template. Currently, there are two ways you can clone courses in the platform: manually or via course feed. We always recommend trying an operation manually before transitioning to using feeds, but cloning via feeds can be really helpful when creating a lot of templates at once.
Clicking on the icon will point you to said higher-level template. If you then edit that higher-level template and return to the lower one, you will see the content has been updated in both places. You then continue to extend the lower one beyond what's already present.
Now here's where it gets tricky: troubleshooting linked templates. There is one principle that can "throw a wrench" into your item creation or editing, and ultimately lead to troubleshooting: higher-level templates will always take precedence over the lower ones in terms of additions and deletions. It sounds simple, right? It Let's say you have two templates: college and course. The college-level template has a course policy that says "No Cheating." The course template then has this policy and also one for calculators in the classroom. Both policies are listed under the Course Policies Item, but the information is split between the two templates. In addition, the course template also contains a course description. In this scenario, you have information housed under the same Item but the information originates on different templates, and have another item (the Course Description) activated on a lower-level template.
Since additions and deletions cascade, here's what can happen:
1) Say a new course policy is introduced for ADA at the college template. This addition will flow down to the course template.
2) Conversely, if the cheating policy is removed, it will disappear from the course template. The calculator policy on the course template will still remain.
3) However, if the course policy category as a whole is removed from the college template, it will take everything off the course template related to policies, including the calculator policy.
4) In a similar manner, if the college template has a course description added, since there is only space for a single course description item on each syllabus, it will override the description that was already in place on the course template, effectively deleting it.
Moral of the story? Be very careful when adding and deleting items from higher-level templates.