Customer onboarding guide

Who should join from your company

• One business owner or executive sponsor who can approve process decisions.
• An HR or people-operations contact for employee records and life events (hires, moves, leavers).
• A payroll or finance contact if you will run pay, issue invoices, or reconcile accounts.
• An IT or security contact for user access, email domains, single sign-on (SSO), and integrations.
• Optional: a department lead for each module you plan to enable in the first wave.

What to provide before onboarding starts

• Legal company name, trading name, country of operation, and operating entities.
• Preferred company subdomain or branded login hostname (if used).
• List of first users and their roles (who administers, who only uses a module).
• Which modules belong in the first go-live wave (start with a small set).
• Current systems to keep connected or replace (payroll export, accounting, identity).
• For payroll, HR, or time modules: pay-period close dates, who owns leave rules, and who approves exceptions.
• Sample, non-production examples for training—never email production secrets or full live payroll files.

Requirements workshop

• Describe the work that causes the most pain today (late data, approvals, reconciliation, requests).
• Agree the first end-to-end path: which modules, which roles, and how work passes between them.
• Capture open questions: country settings, data migration, integrations, and training capacity.
• Define go-live success checks (for example: a trial pay run, one approval route completed, one support ticket closed).

Configuration and validation

• Your platform contact enables licensed modules and base company settings.
• Your administrators invite users and assign module roles.
• Complete each module setup checklist (see the matching module article).
• Run a guided check with synthetic or agreed sample data.
• Close gaps before training larger groups of staff.

Training and go-live

• Train administrators first, then everyday users for the modules in scope.
• Keep the how-to guide and module articles handy during the first weeks.
• Go live with a clear support path (internal owner and platform contact).
• Add the next module wave only after the first path is stable.