Uber Parent Setting explains how ALTA's "Uber Parent" hierarchy works — which organizations receive flow-down benefits and how far down the family tree those benefits travel. Anyone configuring or managing organization hierarchies in ALTA needs this page.
Made with DASH A.i.The Uber Parent is the top-level organization in a hierarchy. When an Uber Parent is established, certain benefits or settings automatically "flow down" through the family tree — but only up to a defined depth. Understanding this prevents misconfiguration where deeper-level orgs are expected to inherit benefits they won't actually receive.
Key points:
Made with DASH A.i.The core rule governs exactly how many generations below the Uber Parent will inherit flow-down benefits.
Rule summary:
In practice: Before adding a new organization deep in an existing hierarchy, confirm how many levels already exist between that org and the Uber Parent. If the new org would land at Level 4 or deeper, plan accordingly — it will need its own direct configuration rather than relying on Uber Parent flow-down.
Made with DASH A.i.This section is currently empty in the source page.
Suggested content for admin review: Consider adding a one-paragraph plain-language description here, such as: "The Uber Parent setting defines the root organization in a multi-level hierarchy. It controls which downstream organizations automatically inherit shared benefits, settings, or pricing — saving administrators from having to configure each org individually, as long as they fall within three levels of the Uber Parent."
Made with DASH A.i.This section is currently empty. Based on the documented business rule, the following practical guidance may help administrators:
Tip — Audit hierarchy depth before onboarding: When adding a new client organization under an existing Uber Parent, map out the full family tree first to confirm the new org lands at Level 3 or above.
Tip — Inheritance stops silently: Organizations beyond the great-grandchild level won't generate an error — they simply won't receive flow-down benefits. Verify inherited settings are present after creating any deep-level org.
Tip — Restructuring can restore benefits: If a Level 4+ org needs flow-down benefits, consider whether the hierarchy can be restructured, or whether a new Uber Parent relationship should be established for that branch.
Made with DASH A.i.This section is currently empty. The steps below are inferred from the documented business rule — an admin should verify and expand these before publishing.
In practice — Establishing an Uber Parent relationship:
Admin note: Screenshots of the system screens used to set the Uber Parent field should be added here once available, to make this step-by-step fully actionable.
Made with DASH A.i.This section is currently empty.
Suggested content for admin review: Use this space to capture edge cases, historical context for why the three-level limit exists, or any exceptions that have been approved. For example: "If a client's org structure requires benefits beyond Level 3, escalate to [team/role] for a manual override assessment."
Made with DASH A.i.This section is currently empty. Suggested keywords for search and discoverability (admin should confirm these match your taxonomy):
Uber Parent · organization hierarchy · flow-down benefits · family tree · child organization · grandchild · great-grandchild · hierarchy levels · org settings · inheritance
Made with DASH A.i.This section is currently empty.
Suggested links for admin review: Once identified, link to any SOPs covering: organization setup/onboarding, benefit configuration, hierarchy restructuring, or parent-child org relationships. This page is a natural companion to any SOP that involves creating or modifying multi-level org structures.
0 files attached to this page