Business email in a team: a practical checklist for joining, changing roles and leaving

Assign responsibilities before somebody starts

In small teams, responsibility is often distributed informally: management owns the domain, an agency knows the provider and an employee manages the mailboxes. While everyone is reachable, this is barely noticeable. During illness or a staff change, however, it must be clear who approves a new address and who may implement changes technically.

Keep a short operational record without passwords. It should name the domain, provider, responsible people, responsibility for contracts and the secure location of credentials. Add an approval route for new accounts and sensitive changes. The document should enable a substitute to contact the right person; it need not become extensive IT documentation.

Prepare the first working day with a clear request

The manager supplies the name, start date, role and required communication routes in advance. Decide which personal address makes sense and which role addresses the person will also use. A consistent naming convention helps later retrieval; document exceptions instead of creating several similar spellings without control.

Technical setup is followed by joint acceptance testing. Have the new person send a message to an internal and an external test address and receive a reply. Check the sender name, signature, calendar and agreed devices. A signed tick box does not replace this brief practical test. Record outstanding tasks and who will complete them by when.

1. Start date, name and required role approved
2. Account and appropriate licence checked
3. Secure sign-in and recovery route explained
4. Sending, receiving and sender presentation tested
5. Contact for faults and changes known

Separate personal access from shared tasks

A shared task does not automatically mean everyone should use the same password. Clarify whether a role address should merely forward messages or several people need to work under it. An alias, a group and a shared mailbox serve different purposes. Have the appropriate option determined for your provider and licence scope.

A simple rule supports collaboration: permissions follow the task and are reviewed whenever it changes. Someone temporarily handling invoices does not necessarily need permanent access to all commercial messages. Document owners for jointly managed addresses and decide who answers. Otherwise, either two people reply or nobody does.

Multifactor authentication belongs in the technical review. Microsoft describes different possibilities depending on the environment and licence. Have the appropriate option reviewed and test the recovery route too; an unprepared change can lock employees out. Microsoft: set up multifactor authentication ↗

A role change deserves the same attention as a new starter

Old permissions can easily remain in place during internal moves. Check not only what is newly required but also what can be removed. Update role assignments, contact information and signatures. Inform affected colleagues who will make decisions in future. The technical change is only part of the actual handover.

Carry out brief, regular inventory reviews. Ask responsible people which addresses are actively used, where cover is missing and which accounts have no identifiable owner. Record the results in the same list. Many individual cases then become a manageable operational process without starting from scratch each time.

Plan departures with timing, responsibility and evidence

A departure request needs a binding time and a business-approved decision about data. Before technical implementation, clarify which business matters remain open and who will take them over. Access changes, required content, devices and subsequent licence decisions belong on one task list. Private content and legal retention duties require separate assessment.

Block access at the agreed time according to the documented provider process. Afterwards, check that the intended effect occurred. Then test the approved communication arrangement, such as suitable information about cover. Deletion or licence removal follows only once the consequences for required data and services are clear. The specific sequence may vary by environment.

Start with properly configured mailboxes and signatures

In its Business Email package, Bissolux sets up up to five new mailboxes and five aliases with one provider on an existing domain. Basic DNS setup, testing, a joint handover and an HTML signature with up to five personal variants are also included. This is a specific starting point for small teams establishing their business communication afresh.

Order the package with its clearly defined scope. The domain and ongoing provider fees are separate. Complete implementation of an HR process, migration of old data, permanent support and special security policies are not automatically included. Use this article to prepare your responsibilities and clarify additional technical work before commissioning it. View the Business Email package with signatures ↗

Your decision in practical steps

1. Documented the domain, provider, responsibilities and cover
2. Created new accounts only with business approval
3. Practically tested sign-in, sending and receiving
4. Assigned a responsible person to shared addresses
5. Planned role changes and departures with a verifiable process

Frequently asked questions