only 1 admin member
Permalink
I am trying to quantify the risks of only having 1 account with admin permissions in our Concrete5 setup. I could do with a list of common CMS maintenance operations that only an officer with admin rights could perform, and therefore if this officer was off long term what knock on effect would that have on the overall management of the site/CMS. I appreciate its normally a concern when too many officers have admin membership, rather than too few, but it does need considering.
Having said so, here are my thoughts on the subject.
Concrete5 has a very flexible and powerful permission management system.
You have one superuser which is the user with username admin (unless you change it). That user cannot be limited in any way.
You also have a user group called "Administrators" which has many permissions enabled so any user in that group will be able to perform many maintenance and other tasks on the website.
But you can also take advantage of the permission system and create your own user groups or single users with a specific set of tasks. For instance a user with only editing permissions. A user with file management permissions. You can pretty much configure it any way you want.
You can check the documentation which will show you what you can do and how easy it is:https://documentation.concrete5.org/editors/dashboard/system-and-mai...