The discussion revolves around the conflation of server admin and board admin roles in Discourse. nap seeks a way to separate server-level responsibilities (e.g., SSL configuration, file size limits) from content moderation tasks (e.g., category setup). Falco explains that IT admins may not need a Discourse account, as server settings can be managed via environment variables in app.yml, allowing chief moderators to operate without access to sensitive configurations. nap asks if admin privileges can be segmented, but Falco clarifies there’s no fine-grained permission system. nap expresses concern over settings like email configurations and server load parameters being accessible to moderators. pfaffman suggests using app.yml to hide admin settings from the UI, referencing object storage configuration as an example. nap confirms understanding, and nap asks if current admin settings can be exported to app.yml, to which pfaffman replies that values must be manually generated.
The admin privilege seems to conflate the server admin role with chief moderator role.
My question is based on our use-case whereby the IT department setup our Discourse server instance but have no responsibility or interest in running/developing the content within Discourse.
Is there some way in which to separate options that an server admin should be responsible (such as SSL configuration) from tasks that a chief moderator would do, like setting up Categories?
An IT admin responsible for settings SSL, for example, doesn’t even need a Discourse account, just access to the server. Also, most IT-related settings can be set as environment variables on the app.yml making unnecessary IT-access for the web part of Discourse.
This way your ‘chief’ moderator can be a Discourse admin/moderator just fine.
@Falco, that seems to me to be somewhat unfortunate.
There are some fields in the Email section which would be of concern to some server admins which the chief moderator does not really need. For example, the email account and password, the port number to use for pop3 polling, and other stuff.
In addition, there are a number of other Admin parameters that have the potential to affect server load, and I can easily see server admins wanting to control those settings as well. Just a simple example being maximum file size of images and attachments. After scanning all the Admin options, there are a lot of settings which should be controlled by a server admin rather than chief moderator.
The up-shot of my questions is that the public facing team can easily be hampered by the back-end team, though both have legitimate concerns.
Is there perhaps a chief moderator template which removes access to certain parameters from the Admin panel?
I had a look at the link which refers to external storage, but for a new user its a bit confusing.
So, as I understand it, what you’re saying is two fold: (1) all the settings seen in the Admin area can be configured in the app.yml file, and (2) that the Admin area will not display any options which are configured in the app.yml file.