In my app, a customer/user is **assigned** a hierarchy (for example geo-hierarchy) for various purpose such as *reports* (e.g. if assigned at Dehli 'a state' then assumed segregation lower levels of hierarchy such as `city` ), *authorization* (authorized to transact for certain level of geographical location), *responsibility*, etc.

A node in hierarchy may have a parent (if not then it is a root node and there can be only one root node) and one or more childs. For example, if hierarchical structure is defined as `Continent -> Country -> State -> City`, then a `country` will have only one parent as `continent`, but many `states` as child.

I want user to be able to define the hierarchical structure to suit his business needs. As of now there are multiple kinds of hierarchy that user can define and use later such as Geographical, Sales, Product, etc.

My concern is that this all that 'Hierarchy' or 'Hierarchical Structure' seems too techincal a term for a user to understand, especially when

* when translated to another language,
* and when user himself has not defined them but has to select a value from it while doing a transaction.

How can I make it less techincal or more simpler for the user, especially for those who may not have any exposure to systems before? Thanks in advance.