When someone changes roles, their mailbox can contain both unfinished work and messages that belong to their next responsibilities. A useful handoff separates those two needs: first, identify what still needs attention; then decide who should handle new messages; finally, have an authorized workspace administrator review the available mailbox options. This approach avoids treating a role change as a simple account switch. It also gives the departing teammate, their replacement and the administrator clear responsibilities, while recognizing that available controls depend on workspace role, plan and provisioning.
The useful bits
- List active conversations and assign each a named next owner.
- Agree on who handles new messages and what senders should be told.
- Ask an authorized administrator to review available mailbox controls and confirm the arrangement.
Start with the work, not the account settings
Before changing access or mailbox arrangements, have the teammate review recent and important conversations. Identify work that is unfinished, waiting on someone else, or likely to attract a reply after the role change. Search and folders can help organize a review, but the teammate should still read the original messages rather than rely on a summary alone.
For each active thread, record the current status, the next action, its owner and any relevant timing. Include context the next person needs, such as a promise already made or a document they should review. Avoid copying sensitive details into a general handoff document unless the team’s practices permit it.
Make ownership explicit
Assign one person to each open item, even when several teammates will collaborate. “The team will follow up” leaves uncertainty; “Jordan will reply to the supplier after checking the revised dates” identifies a next step. The outgoing teammate should introduce the new owner in an existing thread when appropriate, so the recipient knows who to contact.
Also decide whether the original mailbox needs to remain available for reference, and who should be responsible for reviewing it. Do not assume that an alias is a separate mailbox or an independent login. If the handoff requires a different access arrangement, ask an authorized administrator to review what the workspace supports rather than sharing credentials.
Decide who handles future messages
Choose a clear approach for mail that arrives after the role changes. Depending on the work, that might mean a designated colleague monitors relevant conversations, senders receive a new contact address, or an administrator reviews available mailbox administration options. The right choice depends on the organization’s needs and the controls actually available for its plan, roles and provisioning state.
Agree on the scope and duration of any monitoring, and who will respond to messages outside the original teammate’s responsibilities. If senders need to be redirected, prepare concise wording that identifies the correct contact without exposing unnecessary internal details. Do not promise that messages will be redirected, forwarded or recalled unless an administrator has confirmed the relevant option is available and configured.
Ask an authorized administrator to review options
The teammate and their manager can describe the handoff, but mailbox administration should be reviewed by someone authorized to manage the workspace. Ask that person to check which options are available for this mailbox and role, what permissions or limits apply, and whether any change needs a particular provisioning state. Workspace administration controls are enforced server-side; a plan description or another team’s setup does not establish that a control is enabled for this mailbox.
Keep the request specific: explain whether the goal is continued reference, coverage of new mail, a change in responsibility, or some combination. The administrator can then assess the applicable controls without assuming a particular menu, setting or outcome. Do not send passwords or one-time codes as part of the handoff.
Example: a project lead becomes a specialist
Suppose a project lead is moving into a specialist role while a customer project is still active. The lead lists the open delivery question, the promised follow-up and the teammate who will now own each item. The team agrees who will watch for new project replies and what contact information to give the customer. An authorized administrator reviews the mailbox administration options for this workspace and confirms what arrangement can be applied. The outgoing lead checks that the new owner has the context needed before the role change takes effect.
A handoff note might look like this:
example.com addresses below are fictional.
example.com addresses below are fictional.
example.com addresses below are fictional.
Confirm the handoff with a short check
A plan is not complete just because everyone discussed it. The outgoing teammate, new owner and administrator should confirm their own parts: open work has named owners; the future-message approach is understood; and the administrator has confirmed what was actually changed or remains unavailable. If a control cannot be applied, agree on a practical alternative, such as a named person checking for relevant replies, and make responsibility explicit.
Before access changes, verify that the new owner has the necessary context and that important active threads are accounted for. After the change, confirm through the authorized administrator or the agreed work process that the intended arrangement is in effect. Avoid assuming that a sender’s reply proves mailbox access or routing is configured; confirm each part directly.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction