$100 Website Offer

Get your personal website + domain for just $100.

Limited Time Offer!

Claim Your Website Now

PeopleOps Audit Checklist for Web Teams and CMS Accounts

Anyone who manages a content management system knows the user list is a mirror of the team’s history. Editors who left two years ago, freelancers who finished a campaign, a developer who moved to another project: all of them leave footprints in the list of accounts. This checklist applies PeopleOps thinking to that reality, so that every change in the team has a matching, timely change in your site’s access.

PeopleOps is the Ops Atlas term for running the employee lifecycle as a measured operation. If you want the underlying framing, see the Atlas entry that defines the discipline. The checklist below is our own translation of those ideas into the world of CMS roles, plugins and publishing workflows.

Section A: Establish the source of truth

  • Is there one list of staff and contractors that counts as the official record?
  • Does each person have a lasting staff number rather than a mailbox name? The Atlas observes that mailboxes change after name changes and rehires, so matching records by mailbox produces false mismatches.
  • Do entries carry an effective date, including future dates for planned departures?
  • Is it clear who may change each field, such as job title, manager and contract end date?

If any answer is no, fix this section first. Everything else compares against it.

Section B: Joiners

  • Is the CMS role requested from the record, with the least privilege that lets the person do the job?
  • Is access ready on the first morning, so that no new editor shares a colleague’s login in the meantime?
  • Does the new person receive a short plan for the first thirty, sixty and ninety days, from their manager, by the end of day three, as the Atlas suggests for onboarding?
  • Is a named buddy assigned to answer the small questions, such as how content is reviewed before publishing?
  • For no-shows, are provisioned accounts deactivated rather than left waiting?

Section C: Movers

The Atlas calls movers the forgotten event, and the CMS is where it shows. A writer who becomes a site administrator rarely loses her old editorial rights, and an administrator who becomes a writer often keeps the keys to plugins and settings.

  • Does every change of role trigger a review of CMS permissions, plugin access, hosting panels and analytics views?
  • Is the old access removed, not merely supplemented by the new?
  • Can you list everyone who currently holds the administrator role and justify each name?
  • Where a provisioning protocol is available, can role changes be pushed as updates to the existing identity, instead of creating a second account? One open protocol built for that purpose is SCIM 2.0, published as RFC 7643 and RFC 7644.

Section D: Leavers

  • Is a departure entered with an effective time, ahead of the day, so that access can end precisely when employment does?
  • Is a termination treated as the highest-priority event in the feed to your account systems?
  • Does a daily comparison flag anyone who is ended in the staff record but still active in the CMS? It should alert someone, not wait in a report.
  • Have you written down a promised disable time? The Atlas notes that the NIST control family leaves the exact timing to the organisation, so you must choose and then measure it.
  • Are shared logins, API keys and automation bots rotated or reassigned when their human owner leaves?
  • Have you checked the tools that sit outside single sign-on, such as a separate hosting dashboard or an old staging site?

Section E: Rehires and returners

  • When a former freelancer returns, is the identity reactivated without any of the old permissions?
  • Does the record show the break in service, not a blank gap?
  • Is the returner treated as a joiner for the purposes of onboarding and a fresh access request?

Section F: Contractors and agencies

  • Does every external contributor have an end date on file, and a named internal sponsor?
  • Is somebody responsible for contractors who are managed outside the main staff process? Contractor logins left behind after a project ends are a recurring weak spot in the Atlas’s list, and its documented example company handles contractors through its procurement team.
  • Are agency staff given individual accounts, not one shared login?

Section G: Service and privacy

Web teams often run a quiet help desk without noticing: requests for new roles, password resets, media-library access, and questions about who approves a publish. Treat those requests as a service with a menu, not a stream of chat messages.

  • Is there a short catalogue of what staff can request, with a stated response time for each item?
  • Can people find answers to routine questions without raising a ticket?
  • Do confidential employee matters travel by a separate route that never shows up in a shared view?
  • Is personal data in your CMS, such as author profiles and staff photos, collected for a stated purpose and deleted when that purpose ends?

Turning ticks into a score

Award a point per tick and compare your result by section instead of in total. A team scoring high on joiners and low on leavers has a familiar profile: friendly and quick to welcome, slow to tidy up. Jot the per-section totals onto a single sheet with the audit date and file it, so the next audit shows a trend, not just a snapshot. A rising line in the leaver section is worth more than a perfect score in the joiner section, since the risk sits on the exit side. Pay particular attention to Section D, because an unclosed account is the item most likely to hurt you.

Next steps and related reading

Pick the three weakest items, hand each to a named person with a due week, and repeat the audit a month later. For general website hygiene that complements this exercise, see a step-by-step website development checklist for business owners“>a step-by-step website development checklist for business owners, and for the collaboration side, read how a modern CMS smooths teamwork and content handling“>how a modern CMS smooths teamwork and content handling.

Finally, remember the Atlas’s caution: this is operational guidance, not legal advice, and its own entry flags the legal material it cites for periodic re-verification. If your audit touches employment or privacy law, confirm requirements with a qualified adviser in your jurisdiction.

Related Posts

AIOps for CMS and Marketing Teams: Ten Questions Answered

Ten practical questions web teams ask about AIOps, from plugin-update outages to holiday traffic dips, answered with evidence and CMS-flavoured examples.

Read More

A Beginner’s Weekly Review for Your CMS Website, With Glossary

Learn how to check, clear and plan your website each week: updates, drafts, forms and priorities, plus a short glossary of the terms beginners meet.

Read More

FinOps for CMS Teams: An Eight-Step Starter Walkthrough

An eight-step walkthrough for web and CMS teams: list paid services, assign owners, split shared costs, pick a unit measure and set a simple review rhythm.

Read More

Three Ways to Run a CMS Go-Live Checklist, Compared

Memory, a written card or automated gates: how each approach to a CMS go-live checklist feels in practice and which team it suits.

Read More

Six DataOps Myths Web Teams Keep Believing, Corrected

Six common myths about DataOps, from DevOps-with-SQL to learned baselines, corrected for people who run websites, feeds and reports.

Read More

From Web Developer to MLOps Engineer: A Year-One Career Story

A fictional web developer inherits a recommendation model and learns MLOps in twelve months. Her story shows which web skills carry over and what to learn.

Read More
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
0
Would love your thoughts, please comment.x
()
x