I am trying to quantify risks with the current 'management' and roles & resp[responsibilities of our websites 'content management system' (concrete5). I have never administered a content management system for a website before, but my overall understanding on permissions is there is an admin level role which allows overall control, and then there are author level roles, which allow a number of users to edit content on specific pages or areas of the site. My concern, from a contingency perspective, is we only have 1 officer with admin permissions on the CMS, and the others are only author level roles. The concern being if the 1 current admin was unavailable for example ill health for a few months, what would grind to a halt in terms of the overall CMS management?
Back to the 'I have never administered a content management system for a website before' - if you are a CMS admin, what activities/maintenance/monitoring requires admin level permissions in a solution, or put another way, if nobody logged in as an admin for numerous weeks, what could the knock on effect be? I was also hoping to establish some standard maintenance checklists that the CMS admin has to perform, so if they were unavailable another officer could pick up their duties and would have an easy 'how to guide' on which to follow. Ideally supplemented with formal training.