Back to Product Development PortalCurrent-state process
Onboarding
Customer files → Initial Onboarding Sheet → separate uploads.
Draft for validation. The flow is reported by the team and clarified by Katie, with workbook structure checked. It has not been validated against a complete account walkthrough.
Where the files go
| Customer source | Initial Onboarding destination |
|---|---|
| DEPT-ASSET · Departments | Shifts |
| DEPT-ASSET · Asset List | Assets |
| OP-WEB-CHECK · Operator Log | Operators |
| OP-WEB-CHECK · Webusers | WebUsers |
| OP-WEB-CHECK · Checklist Questions | Checklist tabs by applicable asset type |
| DEPT-ASSET · WiFi Settings-If Applicable | No matching internal tab; configuration handoff to confirm |
Review before upload
- Confirm conflicting badges, employee status and uncertain asset identifiers with the customer.
- Separate fields needed for access/configuration from optional reporting detail; do not remove access rules by simplifying intake.
- Preserve checklist answers, expected response and alert/alarm/lockout behavior. Missing values require clarification.
- Flag long checklist questions. The reported 62-character limit, including spaces, needs device/firmware verification; never silently truncate safety wording.
- Customer Webusers collects names and email; the internal WebUsers tab has additional role/site/configuration fields. Confirm who chooses those values.
Open: file format and upload order; department/shift configuration; Wi-Fi handling; import success checks and failed-row correction; company/site and device shipment gates.