Best practices for handling overlays with varying dimensionality in OneStream

We are designing a planning solution where overlays will be used across accounts with very different levels of dimensionality.

For example:

Some accounts have minimal dimensionality (straightforward base members for input).

Others require navigating through multiple UDs before reaching the base intersection.

Ideally, I’d like users to be able to choose their drill-down path until they reach the correct base intersection for data entry.

Has anyone implemented a design pattern or approach that balances these differences effectively?