Remove old website access when a working relationship ends

Access should end when the work does

Website access often grows one task at a time. A staff member edits trading hours, a designer updates a page, or a supplier connects a booking tool. The risk is forgetting those permissions after the task or working relationship ends.

Removing old access is a simple business control. It reduces the number of accounts that can change public information, view enquiries, or alter settings, without interrupting the people who still need to work on the site.

Review the whole website path

Start with the website editor, then check the services connected to it. Depending on the business, that may include the domain account, hosting, forms, booking system, analytics, shared files, and social profiles linked from the site.

Write down the person's name, what they can access, why they need it, and who approved it. Avoid publishing this list or storing passwords in it. The purpose is to make ownership clear, not to create another copy of sensitive information.

Remove access in a safe order

Confirm that the business owner or current administrator can sign in before removing anyone. Transfer ownership of pages, files, forms, and billing where needed. Then remove the old user, revoke shared links, and change any password that was knowingly shared.

Afterwards, test the public website and its main enquiry or booking path. Record the date of the review and the person responsible for the next check. This creates a useful handover trail without exposing technical details.

Make access review part of website care

Do not wait for a security scare. Add an access check whenever a staff member leaves, a supplier finishes, or responsibility for the website changes. A short scheduled review can also catch accounts that remained active because nobody owned the cleanup.

MDP Studio's public security portfolio shows how clear evidence and trust boundaries make technical work easier to assess. For a small-business website, the practical version is straightforward: know who can change what, keep only the access still needed, and leave a clear owner for the next decision.