Your practice
You (or your client, through you) name who’s allowed to trigger a joiner, mover, or leaver request, what a role change should and shouldn’t grant, and how fast a termination request needs to move.
Joiner, mover, leaver Arrivée, mutation, départ
Onboarding, elsewhere on this site, is about launching your practice’s account with us. This page is about something else entirely: what happens on your client’s side every time they hire, promote, transfer, or let someone go. New-hire provisioning, role-change access, and termination deprovisioning are their own recurring, ticketed request type — not a sub-task of a general access request, and not something we assume you’ll remember to ask for.
You (or your client, through you) name who’s allowed to trigger a joiner, mover, or leaver request, what a role change should and shouldn’t grant, and how fast a termination request needs to move.
We work from the request you send — provisioning a new hire’s access on the agreed profile, adjusting a mover’s access to match their new role, and deprovisioning a leaver’s access on the date and scope you confirm.
For a client who already has a hiring, promotion, and termination process, but whose IT access changes happen whenever someone remembers to email about it — instead of a request type with its own expected shape.
Who’s authorized to submit a joiner, mover, or leaver request (usually HR or a manager, not the employee themselves), the standard access profile for common roles, and how far in advance a termination request should ideally arrive versus how it’s handled when it doesn’t.
What you get: A joiner, mover, or leaver event that follows the same documented path every time, instead of depending on whoever remembers to send the email that week.
What we hand back: A lifecycle-log entry naming what changed, for whom, on whose request, and what (if anything) is still open.
Provisioning is fast when "new sales hire" maps to a known access bundle. Without that mapping, every new hire becomes a one-off discovery conversation instead of a request.
A termination request should never depend on a manager’s personal email to someone they know on the delivery side. Name the authorized requester and the fallback if that person is unavailable.
An amicable resignation with two weeks’ notice and an involuntary same-day termination are different requests with different timing needs. Naming both in advance means the urgent one doesn’t have to be improvised.
Mailbox conversion, forwarding, retention period, and who can request access to it later all need a default your client has actually decided — not a judgment call made the day someone leaves.
No — Onboarding elsewhere on this site is about launching your practice’s own account with us. This page is about your client’s employees: what happens on their side every time someone joins, changes role, or leaves. Different process, different page.
As fast as the urgency tier and authorized-requester chain you’ve named allows — this page doesn’t promise a universal turnaround time, because an amicable two-weeks-notice departure and an urgent same-day termination are genuinely different requests.