Municipal website access handoff: when a staff member leaves
A practical checklist for municipal managers to remove departing staff access, transfer website responsibilities and keep publishing and form delivery working.
On this page
A municipal website access handoff should leave authorized staff able to publish while removing the departing person's access at the approved time. Check the website editor and its supporting services, transfer ongoing responsibilities, and verify the result. Passing along a password is not a complete handoff.
Website offboarding is the process of removing access and reassigning the work when someone leaves a role. For municipal managers, the job is to coordinate the people who approve the change, administer accounts and keep resident services running. Use this checklist with those owners rather than making unfamiliar account changes yourself.
What belongs in a municipal website access handoff?
Start with an account list that covers every service the departing person used to manage the website. Ask the provider to review it with you. The website editor may be only one part of that list.
CIS Safeguard 5.1 (opens in a new tab) calls for an inventory covering user, administrator and service accounts. Apply that inventory approach to the services your community actually uses:
| Service to check | Handoff question |
|---|---|
| Website editor, or CMS | Who can publish, manage users and change settings? |
| Domain registration | Who can manage the domain and receive renewal notices? |
| DNS and hosting | Who can change where the website points or request technical work? |
| Forms and resident requests | Who receives submissions and can read stored responses? |
| Alerts and mailing services | Who can send messages or manage subscriber access? |
| Analytics and search tools | Who can manage the property and invite another user? |
| Vendor support portal | Who can authorize changes on the government's behalf? |
Record the service owner, account identifier, current permissions and the action needed. Keep passwords and recovery codes out of this checklist. Use the organization's approved credential storage and transfer process.
Who sets the access-removal time?
The authorized manager or HR contact should give IT and the provider a clear effective time, with a named person responsible for confirming completion. Plan replacement access before a scheduled departure. An urgent departure needs the same coordination without waiting for a training session or a finished handoff document.
CIS Safeguard 6.2 (opens in a new tab) recommends disabling accounts immediately upon termination, access revocation or a role change. That is security guidance, not a statement of a Michigan employment-law deadline.
Do not leave unnecessary access active because an agenda still needs posting. Assign the next update to an authorized employee or arrange for the provider to publish it through the established support process. Confirm who can approve that work if the usual contact has already left.
How should replacement access be prepared?
Give the replacement an individual account with permissions suited to the assigned work. An employee posting meeting documents does not automatically need authority to create administrators or change hosting settings. The CIS access-control guidance (opens in a new tab) covers creating, assigning and revoking privileges across user, administrator and service accounts.
Have the administrator set up the organization's required multifactor authentication and recovery method. The replacement should sign in successfully using their own approved credentials before a planned handoff closes. Do not make their access depend on the departing employee's phone or inbox.
Then practice a real publishing task in a safe area: locate the page, save a change, preview it and find the result. Use the municipal website staff training guide for the learning portion of the handoff. Keep technical administrator duties assigned separately where the platform supports that separation.
Is disabling the login enough?
Ask the administrator to check existing sessions and other credentials as well as the main account. A session is the signed-in state that can keep a browser connected after the initial login.
Microsoft's access-revocation documentation (opens in a new tab) explains that applications can issue their own session tokens, which Microsoft Entra ID cannot directly revoke. The exact behavior depends on the application. A disabled central account alone is not proof that every connected service has ended access.
For each relevant service, ask the provider to confirm:
- The person's account or permissions have been disabled or removed.
- Active sessions have been addressed using that service's supported process.
- Shared credentials the person knew have been replaced where needed.
- Personal access tokens or other separate credentials have been reviewed and revoked where appropriate.
If changing a credential could interrupt an automated task, have the provider update and test that task as part of the change. Record any unresolved access separately, with an owner and a completion deadline.
What needs special attention for the domain?
Confirm that the government retains an authorized way to manage its domain after the departure. Domain administration controls a different part of the website's operation from editing pages.
For .gov domains, get.gov's current domain-management instructions (opens in a new tab) explain how a domain manager adds or removes another manager. They also cover updating contact information and the senior official. Review those entries during the transition; changing one person's CMS access does not update the registrar's manager list.
As a continuity measure, designate another authorized domain manager before a planned departure and confirm that person can sign in. This is a practical recommendation for the handoff. For another domain ending, ask that registrar for its equivalent access and recovery process.
Keep the domain registered to the government. The municipal .gov domain guide explains the broader ownership and management questions to resolve with the provider.
How do you know the handoff is finished?
Check both access removal and the work residents still need. A list marked complete should be supported by confirmation from the people who made the changes and a practical check by the staff taking over.
Before closing the request:
- Obtain confirmation of the affected accounts, actions and completion times from IT or the provider.
- Have the replacement sign in and complete an approved practice update.
- Send a clearly labeled test through the relevant form, using no sensitive information, and confirm the authorized recipient receives it.
- Check that support, renewal and recovery contacts reach the current responsible people.
- Review scheduled notices and pending meeting documents so each has an owner.
Keep the confirmation in the organization's approved internal records location. Do not publish the account inventory or attach credentials to it.
Review access again when responsibilities change, not only when someone leaves employment. Add the review to municipal website maintenance after launch. The handoff is complete when former access has been addressed and the next responsible person can do the work.
Frequently asked questions
Should we delete the departing employee's website account?
Ask the administrator how to stop access while preserving the records the organization needs. CIS Safeguard 6.2 (opens in a new tab) notes that disabling an account rather than deleting it may be necessary to preserve audit trails. Confirm how the CMS handles content ownership before deleting anything. Follow your organization's records procedures separately from the access-removal decision.
Can a former employee keep access to help with occasional updates?
Treat any continuing work as a new, explicitly approved assignment. Define its scope, permissions, approver and end date; do not leave the former employee's broad access active indefinitely. The CIS access-control overview (opens in a new tab) covers managing and revoking credentials and privileges. Review the limited assignment when it ends, including access held in related services.
What if an automated website task uses the departing person's account?
Have the provider identify the task and move it to an approved arrangement with a current owner. CIS Safeguard 5.5 (opens in a new tab) calls for a service-account inventory with an owner, purpose and review date. Test the task after any change. Do not keep personal access active as a substitute for fixing the dependency.
Does removing an email account remove access to every website service?
Do not assume it does. A service may have a separate login or maintain its own signed-in session. Microsoft's access-revocation guidance (opens in a new tab) explains that an application controls its own session tokens. Ask each service owner how access ends, including active sessions, and record the result for the CMS and other website-related accounts.
Keep website work manageable through staff changes.
Explore Muniway's website editing, hosting and staff training for local governments.