Closed SilasBerger closed 3 weeks ago
Some thoughts:
<Interactive>
component, and an <Aufgabe>
-Component internally returns something like <Interactive documentRootId="..."><div>...</div></Interactive>
.<Aufgabe>
, which might have some <TextAnswer>
as a child. Most likely, parents should know their children and children should know their parents.<Aufgabe>
that says "if you have RO or None access on the parent, we just pass that access on to the children as well (in the frontend)? That way, you only need to disable the parent and not all children.Obsolete: see #47.
This task is a direct follow up to #47. The previous task is all about the initial puncture from the student frontend to the DB. In this task, the goal is to set this up in a way that is reusable and well-designed, with admin functionality in mind.
Document roots have an access level (RW, RO, None) defined on the root itself, as well as by user- and student group-based permissions. Allow teachers to change the access level of a given document (root) for (1) everyone, (2) a student group, and (3) a particular student.