What's included
- Asked for by the client, in the portal. In the client portal's Staff changes tab, the primary contact — and any contact they allow — chooses New employee or Employee leaving and fills in a short form: the name, job and start date, and the email address, licenses, equipment and access the person needs; or who is leaving, their last day, what happens to their mailbox, the automatic reply and the equipment to recover.
- Forms that already know the company. The new address is chosen on one of the client's Microsoft 365 domains, the licenses and users come from the last sync, and the equipment assigned to the person leaving is listed to choose what to recover. Without Microsoft 365, the address and the licenses are plain text.
- Or typed in by a technician. The client's sheet has a Staff changes tab with the same two forms and every request of that client; the ticket can be opened for one of the client's contacts.
- One request, one ticket with the right checklist. Each request opens a ticket from the active template of its kind — its subject, type, priority, impact and tasks — with everything that was asked written into the description. The usual new-ticket notifications go out, and no other email.
- The Microsoft 365 steps, one click each. The ticket's Staff change tab shows the request and one button per step. For a new employee: create the Microsoft 365 user, prefilled from the request with its licenses, and create the contact in SLApp, with access to the client portal. For a leaver: block sign-in and sign them out everywhere, set the automatic reply, remove every license, reset the password and deactivate the contact. Each step asks for confirmation first; nothing ever runs by itself.
- The checklist keeps up. A template task can be tied to one of those steps: once a technician has done that step, the task is ticked and an internal note on the ticket says who did what. The temporary password of a new or reset account is shown once, to that technician — never written to a note or the audit log. Every step is in the request's history and in the audit log.
- The person leaving, found for you. The tab finds the leaver's Microsoft 365 user and SLApp contact from the request — by the email address when the client did not pick them — and says how it found them; a technician can link another Microsoft 365 user.
- The rest stays on the list. Converting the mailbox to a shared one or forwarding it, the groups, the computer and the equipment to recover are tasks for your technicians, with what the client asked for in the ticket's description and the equipment listed on the tab.
- Changed their mind? While nothing has been done and the ticket is still in its initial status, the primary contact or the person who asked can cancel the request in the portal: the ticket is closed with a comment saying so, and no email is sent. Your technicians mark a request as done, or cancel it, from the ticket.
- Discreet about leavers. A request about someone leaving is never shown to that person in the portal, unless they asked for it themselves.
📋 Request
- Who is leaving
- Tiago Nunes <tiago.nunes@contoso.pt> · Sales
- Microsoft 365 user
- tiago.nunes@contoso.pt
- Last working day
- 30 Oct 2026 18:00
- Mailbox
- Forward the email to M. Ferreira <m.ferreira@contoso.pt>
- Automatic reply
- Tiago no longer works at Contoso. For sales, please write to m.ferreira@contoso.pt.
- Remove the licences
- Yes
⚡ Actions
- ⛔ Block sign-in and sign out everywhere✓ Done 30 Oct 2026, 6:02 PM by Ana
- 🏖️ Set automatic reply✓ Done 30 Oct 2026, 6:03 PM by Ana
- 🪪 Remove licences
- 🔑 Reset password
- 🚫 Deactivate contact in SLApp
How it works
- 01
The client asks
In the client portal's Staff changes tab — or a technician, on the client's sheet: New employee or Employee leaving.
- 02
A ticket opens with its checklist
From the active template of that kind, with the request in its description; your team gets the usual new-ticket notifications.
- 03
Run the steps from the ticket
On its Staff change tab, one button per step, each confirmed first. A step ticks the task tied to it and adds an internal note.
- 04
Finish the list
Do the rest of the checklist, mark the request as done, and close the ticket as usual.
What it needs
- The client's Microsoft 365 connected to SLApp Helpdesk, for the Microsoft 365 steps and for the domains, licenses and users in the forms. Without it, the requests, their tickets and checklists and the contact steps work the same, and the Microsoft 365 work is done by hand. If connecting a client failed, or it still uses the old connection, an administrator clicks Reconnect.
- Two ticket templates, one for new employees and one for leavers, come ready-made in the language your emails are sent in. Administrators change them — only one of each kind is active at a time — and add general templates for the New ticket form's From template, in Settings → General → Tickets → Templates.
- The primary contact can always ask. Other contacts can once the primary contact allows them in the portal's Contacts, or a technician ticks Can request staff changes on the contact.
- Every technician can open requests and run the steps. A step needs the ticket open: reopen a closed ticket first.
Staff onboarding & offboarding
New employees and leavers asked for in the portal, a ticket with the right checklist, and the Microsoft 365 steps one click at a time.