Access, training, certification,
then accountability.
Four roles, one program. Provision every system, run the same core training, make the new hire prove it on live records, then review at 30, 60 and 90 days. Everything hangs off a single User Onboarding record in Jungo — Salesforce, list views, dashboards, email, SMS, templates, phone, routing, Calendly, Fathom, Zoom, Encompass, the ZMG app and the tools we've built on top of them.
Pick the role you're onboarding
The checklist below rewrites itself for the role you choose — provisioning, training, shadowing, certification and reviews — and your progress is saved separately for each one.
Loan Officer setup
Nothing matches those filters. Widen the phase or system selection.
One record per hire
Everything below hangs off a single User Onboarding record in Jungo. Four layers, one status path, no side spreadsheets.
Core fields
Related records
Standards every user signs up to
Onboarding status path
Core system orientation — every role, day one
The ramp
Who owns each stage and what has to be true before the next one starts.
What each role can see
Data-level permissions, separate from tool access. Build these deliberately — they are far harder to unwind later.
Swipe the table sideways to see every role.
The bonus visibility rule
Loan Teammate / Bonus Participant
Who can be attached
Report filters
Who gets what
Access level by system and role. Use this in the provisioning ticket so nobody has to guess.
Swipe the table sideways to see every role.
The stack behind the checklist
What each system actually is at ZMG, and the specific detail that trips people up.
The dashboard each role gets
Assigned before the start date. If a new hire cannot answer their day from one screen, the dashboard is wrong.
Bonus and survey workflow
What Jungo fires when a loan is marked funded, and the report that lands on the 1st.
Triggered at funding
Monthly bonus report
Training library and admin build
Short videos and written SOPs on the left. The Salesforce work behind the program on the right.
Objects to confirm or create
Automations to build
Three things that break onboarding here
- Person-named Flows. Dozens of active Flows are named after individuals rather than roles — "Create SMS Team Member — Chasten Gerhart", "Key Updates: Automated Email Alerts (Zin)", "SMS: Buying Agent / Loan Processor — Mike". Search the Flow list by first name before you call provisioning done.
- Calendly seats. The Teams plan is at 8 of 8 seats. Sort this out before the start date, not on day one.
- Silent failures. SMS-Magic merge fields fail silently on a case mismatch, EAC drops its Microsoft connection without warning, and dashboards quietly show the owner's numbers instead of the new hire's. All three need an actual test, not a config screenshot.