The intent is to keep the main organization e.g. World Bank.

Any user that gets added with the @worldbank.com domain will get added to the parent. You can then set a "sub domain/group/Child" location to the user so Bob Smith is located in USA, New York, 1 First St. Then we could have Sue Smith located in Australia, Sydney, 56 Queens Road.

I need to see all Tickets for the main organization as we do now but also select the "sub domain/group/Child" location and look at the history of that physical address. End users should have a primary "sub domain/group/Child" and also be able to have additional ones as they could be a manager for more them one.

So if Bob opens a ticket it will be seen under the parent and the primary child.

You should be able to see the parent organization of faults for Bob and/at the "sub domain/group/Child" physical address location. If this is used for say HR or H&S there could be a location environmental issue that is hard to understand without looking at the history for the physical address location over time from multiple tickets from different end users sent from the same physical address location all for World Bank.

I don't want to create 1000 organizations in this fashion

• World Bank - USA, New York, 1 First St
• World Bank - Australia, Sydney, 56 Queens Road

As they will not be all linked under a Globel World Bank organization.

All of this needs to be exportable/importable and updated via CSV as this is easy to manipulate as well as in the App.