Damith C. Rajapakse

> Hi @damithc, could we get your input for this PR. Does this adequately resolve the ambiguity? My view is that the change might actually be more confusing than the...

Yes, it can be a useful feature to have. Need to figure out a way to do it that is not too much extra work to create and keep up-to-date

> Admittedly, the permission-checking code at this page (both versions) is quite a mess. But just to get the record straight, this is the course-wide page? Yes, it is a...

Lowering priority as the user found a workaround.

@fans2619 You are right in that the the current behavior seems to agree with the UI. For practical purposes though, we need to support both approaches, or switch to the...

> @fans2619 @damithc Perhaps a more accurate way to phrase it would be to say "~But~ In sections... this instructor can only...", so that the UI would be consistent with...

Sounds good. Shouldn't we put it at the bottom of the page though, for consistency? There is no good reason for it to be at the top in one page...

> The simplest approach is to follow what "moderation" feature is doing currently, i.e., the entire question is displayed to B only if all the 3 items ("answer", "giver's name",...

Good idea. We are using PlantUML in our other projects already https://se-education.org/addressbook-level3/DeveloperGuide.html In case we migrate our documentation to MarkBind one day, it has built-in support for PlantUML https://markbind.org/userGuide/usingComponents.html#diagrams

These are meant to be simpler _concept level_ views of our features i.e., shows _what_ TEAMMATES can do rather than _how_ it does them. Not sure there are actual components...