SilasBerger
commented
1 month ago Some thoughts:
- Most likely, we need some sort of permissions panel that can be opened for every "persistable" component. Similar to the permissions panel in OneDrive, this would show the current DocRoot permission + all additional user and group permission entries. As soon as the admin changes any of these properties, the panel goes into a dirty state. When the admin hits save, the changes are sent to the API, the panel is disabled, and then updated with the response.
- Architecturally, it would be useful to have some sort of inheritance structure that provides access to this permission panel "for free". Maybe there could be an
<Interactive>component, and an<Aufgabe>-Component internally returns something like<Interactive documentRootId="..."><div>...</div></Interactive>. - Some components will have children, such as an
<Aufgabe>, which might have some<TextAnswer>as a child. Most likely, parents should know their children and children should know their parents. - Could it be useful to provide a setting on e.g.
<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. - Similarly, and probably more importantly: what about pages with maybe 5-6 tasks? From the admin's point of view, there should be an easy way to change permissions im bulk. Especially when it comes to an "ad-hoc" group of students, it would be annoying and time consuming to have to go in and add, say, 5 individual permission entries on 5 different tasks on the same page.
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.