Onboarding a new employee is not just access to a task tracker and a corporate chat. Before the person opens their first work account, they need a number for verification, a mailbox and a channel to reach the network. Hand out these three however it happens — a personal phone, a personal mailbox, no record of the issue date — and the company loses control of its own infrastructure the moment the employee leaves. Here is what to issue and in what order, why the resources must belong to the company rather than the employee, and what to plan before hiring rather than after.

What is issued to a new employee, and in what order

Order matters. First — a number: needed to verify access to work services and as a two-factor channel for the whole probation period. Next — a mailbox: work accounts get registered on it and a recovery channel is configured. Only once there is a number and a mailbox does a proxy channel make sense, because a network without an attached identity is useless. Issuing access in reverse — proxy first, identity later — is a common mistake that leaves an employee working through a shared, unassigned channel for their first week.

Why the resources must belong to the company, not to the employee personally

If a number is registered to an employee's personal phone and a mailbox to their personal account, both leave with the person on departure while the work accounts stay tied to someone else's identity. The correct model: all three resources are issued and paid for on the company's behalf — the number and the mailbox rented through the shared account, the proxy channel bought from the catalogue against the company's balance, not an employee's personal card. Then, when a person leaves, the company simply changes the password to the resource — it does not disappear, it passes to the next person responsible.

Isolating circuits between employees

A shared exit address is the most common reason the work of two formally independent employees ends up linked. Platforms read a connection's origin from its autonomous system, and if two people go online through the same proxy channel, their accounts look like one operator to the receiving side — covered in what an ASN is and why it matters. A ban on one circuit drags the other down with it, even though the two employees never formally crossed paths. The rule: one employee, one dedicated channel — not a shared pool for the whole department.

Logging what was issued: a register with dates

Every issue — a number, a mailbox, a proxy channel — is logged with a start date and a renewal date. Without dates, three months later no one remembers whether a channel issued to an intern who worked two weeks is still active. The easiest anchor is the list of active rentals in the company's account: issue and renewal dates are visible there without a separate spreadsheet, and the same list shows whether a resource is still hanging on an employee who is no longer relevant.

What gets reclaimed on departure — and why it is planned before hiring

On departure, everything issued gets reclaimed: the proxy channel is disabled or reassigned, the mailbox password is changed, and a number used as a second factor is reissued to the new person responsible. Resources registered to the company from the start make this a fifteen-minute checklist. Resources issued from an employee's own accounts turn it into a dispute to untangle. That is why offboarding is settled at the onboarding stage — before a person gets their first access, not after they lose it. How to regularly check that access has not outlived an employee is covered in access audits.

The typical kit and its monthly cost

A new employee's standard kit: one number on monthly rental as the verification and 2FA channel, one mailbox on monthly rental for work registrations, and one dedicated proxy channel at a fixed monthly price. All three are recurring payments, not one-off activation costs, so onboarding cost is budgeted in advance rather than assessed after the fact.

Frequently Asked Questions

Where do you start when issuing access to a new employee?

With the number and the mailbox — the identity that work accounts get registered on. The proxy channel is issued last, once there is an identity to attach the network exit to.

Can a number already used by someone else be issued to a new employee?

Technically yes, but avoid tying a new person to someone else's number history: if the previous employee used it as 2FA for the same services, the overlap complicates both access recovery and any later incident review.

What if an employee left and the access was never documented?

Reconstruct the list after the fact through the transaction history and active rentals in the account — slower than checking a ready register. The right time to start one is now, not after the next departure.

To make sure a new employee's number belongs to the company from the start, not to a personal phone, and stays assigned for as long as needed, use turbon.rent number rental.