New starters, ready on day one.
Nothing sours a first day like sitting at a desk with no login, no email and no laptop. This page shows how a new team member gets set up: what to tell us and when, what happens behind the scenes, and what their first morning looks like. The same process runs in reverse, faster, when someone leaves.
Five steps, one request.
The mapTell us someone is starting
Ideally 5 business days aheadOne request through the portal or your usual channel starts everything. More notice means more calm, especially if hardware needs ordering; less notice is workable, we will just tell you honestly what can and cannot be ready in time.
- Name, start date and role
- Who they should mirror: "set them up like Sarah" answers most questions
- Whether they need hardware, and any extras: phone, second screen, specific software
- Who approves the cost, so nothing stalls on sign-off
Identity & licences
Behind the scenesWe create their account, assign the right licences, and give them access based on their role: the email groups, shared files and applications the job needs, and nothing it does not. Security is set up before they arrive, not bolted on after.
- Account and mailbox created, added to the right teams and groups
- Licences assigned, and any extra cost confirmed with the approver first
- Multi-factor authentication ready to enrol on their first sign-in
The device
Ordered or reassignedA new laptop is ordered, or an existing one is securely wiped and rebuilt. Either way it gets your standard build: the apps your business uses, security tooling, backup, and settings applied automatically. It arrives ready to sign in, not ready to spend a day installing things.
- Hardware quoted and approved before it is ordered
- Device enrolled in management, protected and trackable from first boot
- Delivered to the office or couriered to a remote starter
Day one
The bit everyone remembersThey sign in, enrol their multi-factor authentication, and everything is where it should be: email, files, printers, the tools of the job. They are told how to reach the helpdesk and that no question is too small. First-day questions are expected and answered kindly.
- Ten minutes in their first-day plan for sign-in and setup
- Tell them who we are, so a call from IT is not a surprise
Settled in
The first fortnightSmall adjustments always surface once real work starts: another shared folder, a different distribution list, a piece of software nobody mentioned. Those are quick tickets, not projects. After that, they are simply part of the environment we look after.
Tell us on or before their last day and access is shut off promptly: account disabled, sessions signed out, mail and files handed to their manager, device recovered and wiped for the next person. A leaver who keeps access for weeks is one of the most common ways businesses get burnt, and it is entirely avoidable.
What you can hold us to.
Both ways- A starter who can sign in and work on the morning of day one
- Costs approved by you before anything is ordered
- Access matched to the role, secure by default
- Leavers secured promptly, with mail and files preserved for handover
- Five business days notice where you can manage it
- A "set them up like" name, and who approves the cost
- Leaver notice on or before the last day, every time
Someone starting
soon?
Log the request now with their start date, and it is handled. If you are not yet a Belton client, this is a small taste of how the whole relationship runs.
