Request
Record role, manager, start date, workplace, language needs, device expectations, and the systems the person actually needs.
Employee lifecycle
Starts, departures, leaves, and role changes create small access decisions with large consequences. A clear request, named approver, equipment plan, and closure record keep the work coordinated without pretending every application is centrally controlled.
Turn a hiring note into an actionable setup plan before equipment and access become urgent.
Record role, manager, start date, workplace, language needs, device expectations, and the systems the person actually needs.
Separate business approval from technical execution. The manager or designated owner decides access; IT applies the approved change.
Confirm device source, Microsoft 365 licensing, account naming, multifactor setup path, and any vendor-managed application tasks.
Role and location changes deserve the same discipline as a new hire.
Compare current access with the new role instead of only adding permissions. Remove access that no longer has a business reason.
Plan office, hybrid, or remote changes around equipment, secure sign-in, connectivity, printing, and handoff timing.
Note applications controlled by another vendor, pending approvals, and any temporary access with an explicit review point.
A departure is complete only when ownership, access, information, and equipment have a visible disposition.
Use the employer-approved effective time. Urgent terminations and planned departures require different coordination.
Decide mailbox, files, shared work, forwarding, and application ownership before removing access.
Record completed actions, unresolved vendor work, equipment return status, and the person responsible for each remaining decision.
Prepare this
Continue
Bring the context; keep credentials out of the message.
Book a white-glove introDescribe the interruption, the change ahead, and how your team prefers to be kept informed. A short note is enough to begin a service-fit conversation.