Before deleting a former employee's account, decide how incoming email will reach the next person. Microsoft Learn says deleting the account stops email sent to that address from being received.
Key takeaways
- Decide who will receive the departing employee's incoming email before you remove the account.
- Keep the former employee's address active where customers or partners may still write to it.
- Check the retention settings for each tool, because their clocks differ.
- Search Box Trash for items you can still recover before you finalize deletion.
- Confirm that any legal holds and required records are preserved before deletion is final.
Account deletion mistakes: preserve records before removal
The first error in firm record decisions is treating account removal as a simple administrative cleanup rather than a critical handoff point for ongoing client communication. The risk is not merely about losing past data; it is about losing future inputs that depend on the continuity of that contact point.
Firm administrators must recognize that the act of deletion severs the link between the external sender and the internal team. This loss of incoming email is distinct from the loss of saved files, which may remain accessible under different retention rules. The mistake lies in assuming that because the person is leaving, their digital footprint can be erased without first securing the channel through which new information flows.
Record the incoming-email handoff decision before proceeding with any account removal steps.
Mistake areas at a glance
The three mistake areas below map to specific documented behaviors in the products your firm may use. Each row pairs a decision area with what the named source says happens when you configure or ignore it. Use this table as a quick check before you remove a departing employee’s access.
| Mistake Area | Documented Behavior | Publisher Source |
|---|---|---|
| Lost incoming email | Keep the address active for customers or partners sending to the former employee | Microsoft Learn |
| Misread retention timing | Adjust retention settings to automatically delete data after a set amount of time | Slack |
| Confused trash behavior | Search Trash to locate specific items you can recover or delete manually | Box |
Email handoff. If you assume that deleting an account simply stops communication without planning for continuity, you risk losing contact from clients who still have the old address on file. According to Microsoft Learn, keeping the former employee's email address active is an option specifically because customers or partners may continue sending mail to that address. The same source notes that email forwarding delivers messages to the next person taking over the work.
Retention clocks. Firms often conflate different types of data lifecycle rules, leading to assumptions about how long content remains available. Slack describes the ability to adjust retention settings to automatically delete data after a set amount of time.
Record which retention settings apply to each tool before you initiate any deletion steps.
Before deleting: distinguish incoming email from saved content
Avoid the first major deletion mistake by securing message flow before removing access. The core error here is assuming that deleting a user profile automatically handles future communications. It does not. This creates an immediate gap in your firm’s correspondence records. You must treat the email address as a separate asset from the login credentials. The goal is to ensure that new information continues to reach the person now responsible for the work.
According to Microsoft Learn, you can keep the former employee's email address active. This option exists specifically because customers or partners may continue sending email to that specific address. Keeping it active lets those messages still arrive during the transition period. It allows the mailbox to remain a valid destination for incoming traffic. You should verify this setting before initiating any removal steps.
Once the address remains active, you must direct the traffic to the correct internal recipient. Set up email forwarding so incoming mail reaches the successor’s inbox. The forwarding rule acts as the bridge between the departed employee’s identity and the current staff member’s responsibilities.
Consider the content already stored within that account as well. If you restore a user's account, their OneDrive and Outlook content remains accessible to you, even after 30 days. This fact clarifies the status of saved files and past emails. You should confirm that these assets are preserved before finalizing the deletion sequence. This distinction between incoming flow and stored data is critical. One requires forwarding rules; the other requires retention checks.
During review: separate retention clocks from deletion notices
Retention periods in enterprise tools operate on distinct timers that do not align with a single account deletion event. Administrators must distinguish between the time content remains in a recycle bin, the duration of a preservation hold, and configured automatic deletion schedules for unshared files. Conflating these different mechanisms leads to incorrect assumptions about when data becomes unrecoverable. The following table summarizes the specific retention components and their associated timeframes or triggers based on documented product behavior.
| Retention Component | Timeframe or Trigger | Publisher Source |
|---|---|---|
| Shared recycle bin retention period | 93-day period spanning first- and second-stage bins | Microsoft Learn |
| Preservation library deletion timing | Up to 37 days (30-day minimum plus 7-day timer job) | Microsoft Learn |
| Deletion of unshared files | 30-day grace period followed by permanent deletion | Slack |
| Configured automatic data deletion | User-defined set amount of time | Slack |
In SharePoint and OneDrive environments, the recycle bin operates on a longer timeline. A 93-day retention period spans both the first- and second-stage recycle bins according to Microsoft Learn. This extended window applies specifically to items moved to the shared recycle bin structure. It is distinct from the deletion process for content under a Preservation Hold. Together with the minimal 30-day requirement, this process can take up to 37 days for content to be deleted from the Preservation Hold library as described by Microsoft Learn. Do not treat the recycle bin and Preservation Hold timelines as identical.
Slack handles file retention through configurable settings rather than a fixed universal clock for all data types. Files with no shares have a 30-day grace period and then they are permanently deleted according to Slack. Administrators should verify whether firm files meet this "no shares" criterion before assuming they will persist indefinitely. The distinction between shared and unshared files is critical because it determines which retention path applies to specific documents.
Before assuming erasure: inspect exceptions and trash
Do not assume that deleting a user account removes every associated record immediately. Some platforms retain specific data for legal or business reasons, while others allow manual recovery from storage trash. Check these exceptions before finalizing the deletion, and review client data access controls for the tools that hold firm files.
Legal hold and litigation data A deleted Atlassian managed account keeps data required for legitimate business or legal purposes Atlassian Support. This retention specifically includes data that is part of an active lawsuit, which the platform is required to keep by law.
Reminder and deletion timeline A reminder email follows 10 days after the request. The account becomes permanently deleted after fourteen days have passed since the initial request. Confirm whether any pending legal holds apply to the departing employee’s files during this fourteen-day period.
Trash search and recovery In Box, items moved to the trash do not count towards total storage allocations. You can search your Trash to locate specific items you can recover or delete manually Box. This means that trashed documents are still searchable and available for restoration. Do not equate the absence of a file from the main directory with its permanent erasure; check the trash folder for recoverable content.
| Exception or State | Specific Condition | Publisher Source |
|---|---|---|
| Active lawsuit data | Required to keep by law | Atlassian Support |
| Legitimate business purposes | Data retained despite account deletion | Atlassian Support |
| Trash items | Do not count towards total storage allocations | Box |
| Recoverable items | Can be located through search and recovered manually | Box |
Record which files fall under active litigation holds and which items reside in the trash before the deletion clock expires.
Account deletion reference table by publisher
The following table summarizes the specific retention and deletion rules documented by each publisher. Use this as a quick check before removing an employee's access to confirm which product controls apply to your firm’s records.
| Publisher | Key Deletion or Retention Rule | Supporting Quote Fragment |
|---|---|---|
| Microsoft Learn | A 93-day period spans both first- and second-stage recycle bins; Preservation Hold library deletion can take up to 37 days. | "A 93-day retention period spans both the first- and second-stage recycle bins." |
| Slack | Unshared files have a 30-day grace period before permanent deletion; settings allow automatic deletion after set time. | "Files with no shares have a 30-day grace period and then they are permanently deleted." |
| Box | Items in Trash do not count toward storage allocations; users can search Trash to recover or delete items manually. | "Items in your trash do not count towards total storage allocations." |
Each row reflects the distinct behavior described by that source. Note that these periods describe platform mechanics, not legal hold requirements. For example, while Atlassian Support notes data is kept for legitimate business or legal purposes, the table above focuses on the standard deletion timelines. Verify if any of these accounts contain data subject to active litigation before proceeding with removal.
Illustrative example: email handoff before deletion
Suppose a departing staff member's address still receives messages from two clients. The firm keeps the address active, sets up forwarding to a colleague, and records that colleague's name on the file. After 30 days, the firm checks whether any client still writes to the old address before removing the account. This example is illustrative only.
Keep a record of the preservation decisions
Record the specific decision for how incoming email will reach the next person. Write down who receives that forwarded mail before the account is removed. This entry links the routing choice to the handoff plan for the departing employee's role. For a broader handoff routine, see the Accounting Client Intake Checklist for a Clear Handoff.
Document the product-specific retention behavior you observed during the review. Note which settings apply to unshared files and which apply to shared content. Record any configured automatic deletion periods that differ from standard expectations. Capture the exact status of items in trash or recycle bins at the time of the decision. These notes create a clear trail of what was preserved compared with what was allowed to follow its normal lifecycle.
Next step today: Name the person who will receive the departing employee's incoming email, and write that name down before any account is removed.
Related guides: Firm authentication mistakes: 6 staff access errors · IRS contact authorization: 4 mistakes in firm handoffs.
Departing employee accounts and firm records: FAQ
What account deletion mistakes can affect firm records?
The three core mistakes are losing incoming email, misreading retention timing, and overlooking exceptions and trash. Each error stems from assuming a single product rule applies across all firm tools. Microsoft Learn documents that deleting the account stops email from being received.
How can incoming email reach the person taking over the work?
You can keep the former employee's email address active to catch messages from customers or partners still sending to that address. Microsoft Learn outlines this approach for managing departing staff communications.
Does the same retention period apply to Microsoft 365 and Slack?
No, the products use different clocks. A 93-day retention period spans both the first- and second-stage recycle bins in SharePoint and OneDrive. In contrast, files with no shares have a 30-day grace period before they are permanently deleted in Slack. Microsoft Learn details the longer bin cycle, while Slack specifies the shorter unshared file window.
When does an Atlassian managed account become permanently deleted?
After 14 days, the account will be permanently deleted and the account name will be replaced with “Former user” in products. Atlassian Support states this timeline clearly. Note that data required for legitimate business or legal purposes, such as active litigation data, is retained despite the deletion.
Can items in Box Trash still be recovered manually?
Yes, you can search your Trash to locate specific items you can recover or delete manually. Box confirms this manual recovery capability.