Best way to create a separate VHP new hire landing page without breaking existing menu order

Great setup — this is a clean architecture problem with a clear right answer.

On groups vs. branches: Go with groups. In every multi-brand or multi-population setup I've worked on, groups are more resilient — especially when an HRIS integration is involved. If a sync glitch places a user in the wrong branch, untangling the tree hierarchy is painful. With groups, you just fix the group membership. Docebo's own documentation confirms you can use groups as the visibility condition for both menus and enrollment rules, which is all you need here.

On the menu/home page logic: Your understanding is correct — a user sees the topmost published menu they have access to. So your four groups (VHP New Hire, VHP Employee, Vytalize New Hire, Vytalize Employee) each get their own menu, each scoped to that group only. Menu order determines which one "wins." As long as each user is in exactly one of these groups at a time, the logic is airtight.

One thing I'd add from experience: rather than maintaining four separate onboarding pages, consider building one onboarding page per brand (VHP and Vytalize) and using catalog assignment to control which content each population sees — exactly the approach we used at Playtika across 8 studios. One onboarding page per brand, content scoped by catalog/group. It dramatically reduces the maintenance surface when content needs updating.

On the transition: Use an automatic group triggered by completion of the onboarding learning plan to move users from "New Hire" to "Employee" group. Pair that with an enrollment rule on the Employee group to auto-enroll in the standard learning plan. Clean, auditable, no manual steps.

Reference: Making pages and menus visible to users and Managing Groups.