Before a sales rep's last workday, set three access controls: mail forwarding and inbox rules, the laptop's lock and sessions, and app sign-in.
Key takeaways
- Name an owner for each control and each system before the last workday.
- Check inbox rules as well as the mailbox forwarding setting, then test the block with a message you control.
- Confirm the laptop's inactivity lock has a real value, and collect the device in the same cutoff window.
- Disable the central sign-in account and change every shared login the rep knew.
Why the last workday is the risk window
When a rep resigns or is let go, most of the conversation goes to the deals. Who owns the open opportunities? Who calls the customer on Monday? Who sends the renewal quote that was promised last week? Those questions matter, and they need answers before the rep leaves. Access tends to get handled last, if it gets handled at all. That is the wrong order. A rep who still has a working mailbox, an open laptop session, and a signed-in account for every sales tool can keep reading customer threads, forward them to a personal address, or change records after the handoff is supposed to be finished.
Damage from a departing employee can be ordinary rather than dramatic. A forwarding rule that nobody remembers. A laptop that stays unlocked on a desk. A shared login that the rep knows and nobody has changed. Each one is small, and together they let a former employee keep a foothold in the accounts that your customers trust you to protect.
The fix is not a new product or a long project. It is a short list of controls, an owner for each one, and a cutoff plan that is agreed before the final day rather than improvised during it. This post covers three access controls to set before the last workday:
- Mail, forwarding, and inbox rules
- The laptop and its sign-in sessions
- App access through your sign-in service
Each of these is a setting, a checklist item, or a task that someone with admin rights can complete. The examples assume a small B2B firm with a shared CRM, a Microsoft-style mail system, and a company-issued laptop. If your setup differs, the same questions still apply. Where does the rep's mail go? What can the laptop reach? Which systems sign in with which credentials? Write the answers down. You cannot cut off what you have not listed.
Who owns what
Before touching any setting, name an owner for each part of the handoff. In a small firm, one person often wears several hats, which makes it easy for a task to fall between chairs. The rep's manager usually owns the deals and the customer handoff. Whoever runs IT or your outside provider owns the mail, the sign-in service, and the laptop. Write these owners in the offboarding checklist next to each task. When the next rep leaves, the same list should work without anyone having to remember which screen to open or which admin to call.
The owner also decides what counts as done. For mail, done means forwarding is off and the new owner can read the mailbox. For the laptop, done means the device is back in your hands and signed out. For apps, done means the rep cannot sign in to anything the company uses. Write those definitions down, because "I think we did it" is the sentence that causes gaps.
Control 1: Mail, forwarding, and inbox rules
Start with mail, because it holds the most customer history. Check two places that people often miss. The first is mailbox forwarding, which an administrator sets for the whole mailbox. The second is inbox rules, which a user can create without asking anyone. Both can send messages to an outside address, and you need to check both.
Microsoft's guidance makes the distinction clear. Users can configure Inbox rules to automatically forward messages to external senders, and Microsoft notes this can happen deliberately or as a result of a compromised account. Control external email forwarding and fix 5.7.520 errors A rep does not have to have bad intent for this to matter. A rule set up during a busy week to catch a customer's replies can keep sending mail to a personal inbox long after the rep is gone. Nobody checks it because nobody remembers it exists.
The good news is that one policy change can cover both paths. Microsoft says that disabling automatic forwarding disables any Inbox rules that users have, and any mailbox forwarding that admins have set, that redirect messages to external addresses. Control external email forwarding and fix 5.7.520 errors Before you rely on that, confirm the setting in your own environment. A policy you believe is on and a policy that is actually on are not the same thing. Open the setting, read its value, and write down what you found and when.
If your organization blocks external forwarding, a blocked message may come back with the code 5.7.520 and the text "Access denied, Your organization does not allow external forwarding." Control external email forwarding and fix 5.7.520 errors Seeing that error during a test is a useful sign that the block works. Do not treat the absence of an error as proof, though. Test with a message you control, sent to an address you control, so you know what happened.
You can also manage mail forwarding from the admin center. Microsoft's guide to configuring email forwarding for a mailbox says that the Microsoft 365 admin center can be used for that. Configure email forwarding for a mailbox in Exchange Online Use that page to find where the forwarding setting lives in your environment. Then copy the exact steps into the offboarding checklist, so the next admin can repeat them without guessing.
For the rep's mailbox itself, decide three things before the last day.
- Who reads it next. Name the new owner, usually the account manager who takes over the deals. Give that person access before the rep leaves, so no customer email falls into a gap between the two of them. For saving deal evidence from that mailbox, see the departed rep mail steps.
- What the outside world sees. Set an out-of-office message that names a colleague and gives a working contact route. Keep it short and plain. Do not promise a response time that nobody has agreed to keep.
- How long it stays. Ask whoever handles your records or legal questions how long the mailbox should be kept. The answer depends on your contracts and local rules, so do not guess and do not delete a mailbox just because the person left.
Check the rep's phone, too. If the rep set up work mail on a personal device, that device is part of the mail path. On the last day, ask the rep to remove the work account from the device, and confirm afterward that the account no longer appears on it.
Control 2: The laptop and its sign-in sessions
A laptop left signed in is an open door, even in a locked office. Whoever picks it up does not need the password if the session is still active. That is why the laptop control matters even when the rep is leaving on friendly terms.
Windows has a setting for this. Windows detects user-input inactivity of a sign-in session by using the security policy setting "Interactive logon: Machine inactivity limit." Interactive logon: Machine inactivity limit The setting counts elapsed seconds of inactivity. It can range from zero to 599,940 seconds, which Microsoft describes as 166.65 hours. Interactive logon: Machine inactivity limit A long timer leaves an unattended desk open for longer. Choose a value that suits your office. A shorter timer protects an unattended laptop better than a long one, but it can also interrupt real work. Pick one, write it down, and apply it to every company laptop, not only the one the rep uses.
Watch for the value that turns the protection off. Microsoft says that if the machine lock is set to zero or has no value at all, the policy is disabled, and a user sign-in session is never locked after any inactivity. Interactive logon: Machine inactivity limit So when you audit a laptop, check the value itself, not just whether a policy exists somewhere in your tooling.
Locking stops someone from using the keyboard in front of the laptop, so pair the laptop control with the account controls later in this post.
Put the laptop plan into three stages.
- Before the last day. Confirm the inactivity lock is set to a real value on the rep's machine, using the laptop checks before corporate access. Make sure the rep's working files are stored in company systems, not only on the device. If the rep keeps notes in a local folder, move them now while the rep can still explain what they are.
- At the cutoff. Collect the laptop in the same cutoff window, straight after you disable the rep's account. A device that stays with the rep after the account is cut is a device that someone can still open with a saved session. Record the serial number and the time of collection in your asset list.
- After collection. Sign the account out everywhere, reset the password, and then wipe and reissue the device through your normal process, using the wipe limits to check before reissue. Do not reissue the laptop until someone has checked that it no longer holds the rep's sessions or saved passwords.
If the rep used a personal laptop for company work, you cannot collect it, and the job changes. Your task becomes removing company data and company accounts from that machine, and confirming that the removal worked. Ask the rep to sign out of company tools in front of a colleague or on a recorded call, and check the sign-in activity afterward.
Control 3: App access and sign-in
Mail and laptops are only two of the doors. Many small firms have a CRM, quoting tools, file storage, a chat app, a billing system, and a few tools that someone signed up for on a trial and never told IT about. Access to all of them should be controlled from one place wherever possible, because a single place is easier to check on the last day.
If your apps sign in through a central service with multi-factor sign-in, the rep's app list is set by an administrator. The Duo user guide describes it this way: "Your organization's Duo administrator determines which applications you can access." Duo Central - Duo User Guide That means removing app access is an admin task, and it should be done by the person who runs your identity system, not left to the rep to tidy up.
The same guide also tells users what to do when an app is missing: "If you don't see an application you need, contact your help desk." Duo Central - Duo User Guide Plan for that. Before the last day, tell the rep who to call for legitimate handoff questions. Tell the help desk that the rep is leaving, and that any request from the rep's account after the cutoff should be routed to the sales leader rather than fulfilled automatically. That single message prevents a common mistake, where a help desk ticket quietly restores access that was supposed to end.
Work through the app list in this order. This is a checklist order, not the cutoff-day sequence below.
- The central sign-in account. Disable the rep's account at the sign-in service. Disabling is usually safer than deleting, because the account is still tied to history, comments, and records that someone may need later. Confirm the account can no longer sign in to anything.
- Deal ownership. Reassign open opportunities, forecasts, and scheduled tasks in the CRM. Do this with an admin account, from a written list of which deal goes to which owner, rather than asking the rep to reassign on their own login. The handoff should not depend on the rep's access staying open while someone else is still working out the details.
- Shared logins. List every shared password the rep knew. That includes a shared sales inbox, a social account, a vendor portal, a domain registrar, and a password for a shared drive. Change each one. Store the new values in your password manager, not in a chat message or an email.
- Trial and personal sign-ins. Find any tool the rep signed up for with a work email and never handed over. Move the account to a company login, or close it if nobody needs it. These accounts are easy to forget, and they often hold customer lists and exported reports.
- Mobile apps. Remove the rep from chat, mobile sales apps, and any two-step authentication apps tied to company accounts.
After the cutoff, check the sign-in activity for the rep's account for several days. You are looking for any sign-in after the cutoff time. A single attempt may be harmless, such as an automatic mail client that was not removed. Anything more should be investigated before you close the list.
A simple order for the last day
Most of the preparation can happen in the days before the final workday, while the rep still has a normal schedule and can answer questions. The cutoff itself should be quick and planned.
Before the last workday:
- Name an owner for each of the three controls and for each system on the list.
- Confirm that external forwarding is blocked, and find any inbox rules that redirect mail.
- Confirm that the laptop inactivity lock is set to a real value and not zero or blank.
- Write the deal reassignment list, with the new owner's name next to each account.
- Draft the out-of-office message and the handoff note for customers and partners.
- Tell the help desk about the departure and the routing rule for requests.
On the last workday, in this order:
- Reassign open deals with an admin account, and confirm that each new owner can see the records.
- Move the mailbox to its new owner, or set it up the way your mail system allows, and confirm forwarding and inbox rules are off.
- Disable the rep's central sign-in account.
- Collect the laptop, record the serial number, and sign the account out everywhere.
- Reset the passwords the rep knew, and change the shared logins.
- Remove the rep from mobile apps and personal devices, and confirm it in writing.
Illustrative example: a 10-deal handoff
A firm hands 10 open deals from a departing rep to two new owners. An admin reassigns the deals from a written list, then checks that each owner can see the records. The central sign-in account is disabled next. On the checklist, every line is done except one: the rep's personal phone still holds the work mail account, so the owner removes it before the handoff closes.
Access gaps often come from a short list of predictable mistakes
Access gaps often come from a short list of predictable mistakes. Use it as a review sheet before the cutoff.
- Keeping the rep as the owner of a shared login. If the rep knows a password the company still uses, that password is part of the handoff, even if the rep is well liked.
- Forgetting the small tools. Trial accounts, shared drives, vendor portals, and the rep's phone are where access tends to survive the main cleanup.
Keep the list and test it next time
A handoff is not finished when the rep walks out. It is finished when the new owners have the deals and the old access is gone. Ask the new deal owner to confirm they can see the customer records, the mailbox, and the shared files they need. Then confirm, in writing, that the rep's accounts are disabled and the laptop is back in company hands.
Keep the checklist in a shared folder that the admins and the sales leader can both open. After each departure, read it back with the people who did the work and add whatever was missing.
Your next step: today, copy the three controls into your offboarding checklist, each with an owner and a definition of done.
Frequently asked questions
Should I delete a departing rep's account?
Usually not. Disable it on the last workday, since the account still holds history and records.
Is a locked laptop enough?
No. Locking only stops someone at the keyboard, so collect the device and sign the account out everywhere.