The discussion centers on ensuring read-only categories remain truly read-only, even for admins, to prevent accidental posts that could disrupt announcements or mailing-list mirrors. hellekin proposes a warning system for admins attempting to reply or create topics in such categories, encouraging them to quote content elsewhere instead. RGJ suggests a broader solution via a “sudo”-like mode for admins and moderators, referencing an existing feature request. hellekin acknowledges that the admin warning is more immediately feasible than the “sudo” feature. Heliosurge points to an existing theme component that warns admins when replying to closed topics, suggesting it could be adapted to check for read-only category permissions, potentially as a custom theme component. The goal is to preserve the integrity of read-only spaces while still allowing intentional admin intervention when necessary.
Sometimes it’s useful to maintain a read-only category accessible to one or more groups to follow announcements or mirror a diffusion list.
Problem
Since admins can post anywhere, it can happen that an admin will reply or post a topic in such a read-only category unknowingly, resulting in lost discussion or unnoticed intervention, or even in unsolicited email back to the original mailing-list.
Resolution
When an admin tries to reply to an existing topic, or tries to create a new topic in a read-only category, they should receive a big fat warning greying out the composer and asking them to confirm that they indeed want to do this, suggesting they could quote the topic in another, more appropriate space.
There is this TC for the closed topics. Might be able to extend it or create an additional custom Customization > Theme component for the create topic in s closed category.
Maybe though to fit more closely might need to see if can change a bit to check a category for see only permission in category security.