The topic summary says it all!
AI-generated summary
The discussion revolves around whether Discourse’s built-in “admins” group can be renamed. not-ethan clarifies that renaming is not possible due to backend dependencies, though a theme component could alter the name on the frontend. pfaffman questions the need for renaming, suggesting alternative solutions. jeffbyrnes, seeking to align the group name with their grassroots “Steering Committee,” expresses concern about maintaining two separate groups. pfaffman advises creating a new group instead, noting that leadership likely doesn’t need full admin privileges and that renaming would create confusion. Stephen challenges whether leadership truly needs high-level admin powers like accessing backups or personal messages. jeffbyrnes acknowledges the need for broad administrative capabilities to avoid bottlenecks, especially with only three committee members including themselves, and concludes that a separate group is the most practical solution. The consensus leans toward avoiding renaming “admins” and instead using a custom group for leadership roles, reserving true admin privileges for those who require them.
No. The term admin is used all over in the back end of discourse. The best you can do is make a theme component to change the name on the front end.
I wouldn’t recommend it.
What problem is this going to solve? There may be a different way to solve it.
Looking to have a group named “Steering Committee” which is my grassroots group’s leadership, that are also “admins”.
Maintaining two groups seems less than ideal.
Just make a group called that. Those people almost certainly do not need to be admins. It will be much less work to do make a group for those people than to explain to anyone that you have renamed admins.
Does your leadership really need the ability to download database backups, or inspect the personal messages of other users?
Will they ever need to change an API key, or configure an SSO endpoint?
Broadly speaking: yes. I’m one of that leadership & I shouldn’t be a bottleneck to running the site if I’m unavailable.
Said another way: there’s 3 steering committee folks, and I’m one of them.
It seems a separate group is the only way to go though.
Thanks folks!