Structured requests.
Collect user details, service requirements, access needs, and equipment instructions in one structured request. Give IT the context to review the work before setup begins, rather than chasing separate messages.
FEATURES
Clear requirements.
Accountable handoffs.
Give MSP and internal IT teams a complete request, a repeatable setup plan, and a clear owner for each handoff. Onboardinator is in early-access development around the work that connects a joiner or leaver request to completion.
Reusable role
templates.
Capture recurring requirements by role, client, or department. A reusable starting point should still leave room for the exceptions in each request.
Review and approval.
Identify who should review the request and authorize the work. Keep the requested setup distinct from what has been approved, rather than relying on an email thread.
Account-work scope.
Keep Microsoft 365 account requirements with the request: what the person needs, what has been approved, and who owns the work. Separate standard setup from exceptions that need a closer look.
Technician checklists.
Assign device preparation, equipment handover, and access checks to a named owner. Keep these tasks alongside the original requirements so the team can follow through on the whole setup.
REQUESTS, APPROVALS & TASKS
How the features
work together.
Connect the information a requester provides with the decisions and handoffs IT needs to make. Review the requirements, agree the work, and give technicians a clear next step.
FROM REQUEST TO FOLLOW-THROUGH
THE PROCESS
01 / COLLECT DETAILS
A better starting point.
Collect the right details once, apply the relevant workflow, and let your team see what needs to happen next.
User information and service requirements give technicians a clear starting point.
Request context, approval, and technician follow-up belong in the same process.
OFFBOARDING FOLLOW-UP
Account work is one step.
Track the rest.
A departure plan needs decisions about access, mailbox and file ownership, and equipment return. Separate the actions your team must take from the checks that confirm the handover is finished.
Follow the product’s progress.
Join early access.
Join the list for updates on requests, reusable role requirements, and the handoffs that keep onboarding and offboarding moving.