The job of this console
Walk phases in order: identity and config, people masters, time rules, approvals, then optional modules. Tick only what the org has actually proven in the live consoles.
One-time day-one checklist with phased guidance, docs, console links, and an automation playbook.
Scroll to Flowcharts. Scenario: Complete day-one customer setup.
Day-one runway
The setup checklist is one-time day-one guidance — phases, docs, console links, and an automation playbook — so a new tenant is not configured by folklore.
/admin/setup-checklist
Org flag appconfigEnabled
HR Admin · Org Admin · implementation partner
Walk phases in order: identity and config, people masters, time rules, approvals, then optional modules. Tick only what the org has actually proven in the live consoles.
People standing up Tracopus. Day-to-day HR admins return only when a new module is being switched on. Employees never see this page.
Open a phase, follow the linked console, complete the work there, return and mark it. Use the playbook for jobs and flags last, after masters exist.
First week of a tenant. Adding payroll after HRMS is already live. A new country pack. After an incomplete go-live, to see what was skipped.
Open the next incomplete item, follow the console link, then mark done.
flowchart TD
A[Open Setup checklist] --> B[Scan remaining]
B --> C[Open next item]
C --> D[Follow console / docs]
D --> E[Mark done]
E --> F{More remaining?}
F -->|Yes| C
F -->|No| G[Hand off to templates]
The checklist is guidance over Employee, Project, PO, Task, App Config, and related consoles. Completing a row does not create isolated business data.