Lorixen.
EN

When a Staff Member Leaves: Access Cleanup for an Internal App, Hour by Hour

Short answer: When someone leaves, deactivate their account in your internal app rather than deleting it, end their active sessions at once, and rotate anything they could have copied, such as shared passwords and API keys. Do the urgent part within the first hour, the tidy-up of ownership and assigned work within the first week, and a review of what the person could see and export within the first month. Deactivation keeps the history intact, so old notes still show who wrote them.

This plan is general good practice. Employment rules about final pay, equipment return and data handling differ by country, so use official employer guidance or HR advice for those parts.

Why "delete the user" is the wrong move

If you delete the account, the app may erase or blank the name from every job note, invoice approval and quote that person touched. Reports then show "unknown user", and nobody can answer "who agreed that discount?". Deactivation does the opposite: the person can no longer sign in, but their name stays on the past. Make sure your app has this distinction. If it only offers "delete", ask your developer to add a status field and a check at sign-in.

Hour one: stop access

Do these before or during the exit conversation, depending on how the leaving is happening.

  1. Deactivate the account in the internal app so new sign-ins fail.
  2. End live sessions. A deactivated user who is still signed in on a phone may keep working until the session expires. Your app should be able to revoke all sessions for a user. If it cannot, ask for that to be added.
  3. Remove single sign-on or email access if the app sits behind your company email login.
  4. Switch off personal tokens. Check for API keys, mobile app tokens and calendar feeds issued to that person.
  5. Change shared secrets they knew: a shared admin login, a Wi-Fi password for the shop floor, a card reader code.
  6. Take the person off alert lists such as new-order emails and out-of-hours text messages, so notices do not land in a mailbox you no longer control.

Day one to week one: hand over ownership

Reassign what they own

Look for records that name the person as owner: open jobs, customer accounts, scheduled tasks, recurring reminders. Filter the app by owner and reassign in bulk to a named colleague. Leaving things assigned to a deactivated user is how follow-ups silently die.

Check automations that use their identity

Integrations are often created under a person's login: a connection to the accounting package, a mail account used for sending, a calendar sync. When the login dies, the integration breaks, usually on a weekend. List each connection, who authorised it, and recreate it under a company-owned service account.

Handle their mailbox and notes

Decide who reads incoming mail to the leaver's address for the next few weeks, and put an auto-reply with a new contact on it. Export or reassign any private notes that hold customer information the business needs.

Update the role list

Remove them from any group, rota or approval chain. An approval flow that waits on a deactivated person will stall invoices.

Week two to month one: review and learn

Review what they could reach

Compare the person's role with what they actually used. Pull the audit log for their last 30 days, looking for unusual exports, bulk downloads or access outside working hours. This is a routine check, not an accusation, and it helps you decide whether any customer needs to hear from you. If you find something that looks like a data breach, check the official regulator guidance in your country about notification duties.

Close the loop on devices

Confirm returned equipment is wiped or re-issued, and remove any app installs or saved sessions from personal phones if staff used them. Written policy on personal devices makes this far easier.

Rotate what is still shared

If any shared credential was missed in hour one, change it now and record where each secret lives, so the next leaver is faster.

Reconcile and archive

Run a last check that nothing is still assigned, scheduled or connected to the deactivated account. Then archive their records according to your retention policy.

One-page leaver card

When Action Owner
First hour Deactivate, revoke sessions, remove tokens Admin
First hour Rotate shared secrets Admin
Day one Reassign open jobs and customers Team lead
Week one Move integrations to a service account Admin
Week one Mailbox cover and auto-reply Office manager
Month one Audit log review, device check Owner

Keep this card where managers can find it. Joiners and movers deserve their own short cards too, because stale permissions from a role change are the same problem in slower motion.

Make it easier next time

  • Tie roles to job titles rather than ticking individual permissions for each person, as the OWASP authorization guidance recommends in spirit with least privilege.
  • Keep a list of every system each person can use. Without it, "remove them from everything" is a guess.
  • Let your app show last sign-in dates so dormant accounts stand out.
  • Ask for a single "offboard" button that does hour one in one action.

FAQ

How soon must access end for a friendly resignation?

At the agreed last working moment, not at the notice date. Many owners schedule the deactivation in advance so it happens on time.

Should we reuse the account for the replacement?

No. Create a new account so the history stays truthful and the new person starts with the right permissions.

What about contractors?

Give them expiry dates when they are set up. A contractor account with an end date removes the need to remember.

Can the app do this automatically?

Often. Linking account status to a staff list or your identity provider means one change cascades to every connected tool.

If your internal tool lacks a proper deactivate, session revoke or audit view, tell us what you have today and we can plan the changes.

Sources

WhatsAppBook a call