Good question…
We have two paths here:
- The fisrt path: As Nethserver is a system for everybody, even for somebody who are not sysadmin, the rules can be only displayed, without possibility to edit.
These rules are displayed only to make things more transparent, and the apprentice sysadmin learn at the same time.
The sysadmin can only deal with these rules with the first setup script choosing how Nethserver will do ( firewall or server only ).
The second path: As Nethserver is very modular, and by consequence, versatile, all the rules are editable… This state let the sysadmin more responsable about these rules…
To prevent any accident, a possibility to cancel the last action ( when things gone bad 
) or the ability to run the fisrt script to make these preset rules back.
And to make a wiki page with the preset rules to inform, learn and eventually create back there rules…
In my point of view, I have a preference for the second path, with the sysadmin more responsable 