The Advent Calendar of Access: A CMS Plan for Seasonal Editors

Every November, a familiar request lands in the web team inbox. Someone needs a temporary editor for the Christmas campaign, a freelancer is covering the January sale build, or an agency secondee is joining for six weeks to get the festive landing pages live. It is all perfectly sensible. The trouble starts when the CMS account is created in a hurry, given too much power, and then forgotten until a January access review turns into a small horror story.

Seasonal editors do not need to be a risk. They just need to be treated like what they are: short-term access with a clear start, a clear job and a clear finish. Get that right and December feels busy rather than chaotic.

Start with a role template, not a favour

A one-off account created for one person is how permissions drift. Instead, build a seasonal editor role template in your CMS before the rush. Keep it deliberately narrow: create and edit their own drafts, upload media to a nominated folder, submit content for review, and preview pages. That is usually enough for campaign copy, festive landing pages and temporary promotions.

Name the account in a way that will still make sense in February. Something like temp-2026-christmas-editor-firstname is not glamorous, but it tells the next person exactly what the account was for. Add the line manager, the commissioning contact and the end date to your access register at the same time you create the login. If the CMS supports account expiry, use it. If it does not, put a calendar reminder in the team diary and assign an owner. A promise to remember is not a control.

The 30-minute induction that pays for itself

You do not need a three-hour tour of every corner of the CMS. You need a short, repeatable induction that covers the things a temporary editor will actually touch. Book half an hour, screen-share, and keep it practical.

Cover the login and multi-factor authentication first. Then show them the draft-to-review workflow, where to upload images, how to add alt text, and what the house style says about dates and prices. Point them to one named person for questions and one backup. Ask them to create a test draft and send it for review while you are still on the call. That single task reveals more than a long explanation.

Finish with the boundaries. No publishing to live without review. No changes to menus, forms or redirects. No installing anything. No sharing the login. If they need something outside that list, they ask the web team. A short induction is not a lack of trust. It is a useful fence.

What never goes to a temp account

Some permissions should stay with permanent staff, full stop. Do not give a seasonal editor admin rights, user management, plugin or extension installation, theme edits, form submission exports, analytics property administration, API keys or anything that touches DNS, payments or backups. Those are not editing tasks. They are platform tasks, and they can cause damage that takes far longer than six weeks to unpick.

Shared logins are another trap. A temp account called christmas-help is impossible to audit and impossible to shut down cleanly. Every seasonal editor gets their own account, even if that means a few more minutes of admin. If your CMS has single sign-on, use it so access can be revoked in one place. If it does not, make sure the local account has an owner and a diary entry.

Give every seasonal account an expiry date

The best offboarding routine is the one that starts on day one. When you create the account, set the end date. When you book the induction, book the offboarding slot in the same calendar entry. When you add them to the CMS, add them to the access register with the same date. This is not bureaucracy for its own sake. It is how you avoid relying on memory during the week when everyone is thinking about mince pies and Boxing Day telly.

If your CMS supports scheduled deactivation, use it and check that it actually works. If it sends an alert, make sure the alert goes to a person rather than a shared inbox nobody reads. A seasonal account with no expiry is just a permanent account with a festive name.

Same-day offboarding, before the goodbye email

When the contract ends, disable the account the same day. Not next week. Not after the January audit. Same day. Revoke single sign-on access, reset any local password, remove the account from editor groups, and check for API tokens or integrations that were created in their name. Reassign any drafts or scheduled content to a permanent owner. If they had upload rights, check the media folder for anything that should not be there.

Then write it down. A two-line entry in the access register is enough: account disabled, date, person who did it, any content reassigned. That record is what makes the difference between a clean handover and a mystery.

Make January's access audit boring

A good seasonal access plan leaves the January audit with very little to find. You should be able to open the register, see every temporary account, confirm it is disabled, and move on. If you find an active account for someone who left before Christmas, you have learned something useful for next December. Add it to the template, not to a mental list.

Seasonal editors are not the problem. Unmanaged seasonal access is. A narrow role, a short induction, a hard expiry date and a same-day exit will get your Christmas content live without handing over the keys to the whole CMS.