Support & operations · Practical guide

Review automated publishing access as well as named users

Named user accounts are removed, but an automation credential can still publish changes to the website.

Healthcare website support desk with a system checklist, telephone and orange notebook.
Know who to call and what help your support arrangement includes.

What to change

Inventory non-human access alongside people. Ask the departing supplier and hosting owner to identify deployment tokens, connected applications and automated jobs associated with the old arrangement. Replace or revoke obsolete credentials through a controlled transition, then test the approved publishing route. The objective is to preserve legitimate automation while removing unexplained ability to alter the site. Keep secret values out of the inventory; record purpose, owner and lifecycle decision instead.

A worked example

Illustrative example

Illustrative test: The incoming supplier can publish an authorised test while the retired route no longer works. The outgoing supplier's named account may be removed while an old automated publishing token still exists. The controlled transition inventories that route, establishes the incoming approved automation and retires the obsolete access. An authorised test proves the continuing process works. Your practice keeps purpose, owner and lifecycle decisions in the record, without copying token values or assuming visible user removal necessarily ended every ability to change the website.

Healthcare website maintenance with infrastructure, a status panel, tools and an operational checklist.
Monitor the useful journey, not just whether a server responds.
Healthcare backup and recovery illustrated by storage copies, an archive folder and a restoration route.
Test whether a backup can restore a usable service.

What this means for your practice

Removing a supplier's visible user account may leave an automated token or connected application able to publish changes. Ask the departing supplier and host to inventory those non-human access routes by purpose and owner. Decide which support the continuing process and which should be replaced or retired through a controlled transition. Test the incoming supplier's approved publication route afterwards. The objective is to preserve legitimate automation while removing unexplained control, not to disable every integration indiscriminately. Keep the actual secret values out of the inventory. A clear lifecycle decision and accountable owner are the useful handover details for each continuing credential.

How to check the result

Every continuing deployment credential has an accountable owner.

A mistake to avoid

Removing visible user accounts does not necessarily remove automation access.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore support & operations services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.