I have several locations that have many of the same settings but, there are a few settigns unique to each location. Is it better to have a parent profile with the similiar settings and then make a child profile for each that has unique settings or is it better to have individual user profiles for each location and include the similar settings and unique setttings?

For organizational purposes it helps to use the Parent Profile so that when I change something, I only have to do it once on those. I do not know the affect it will have on login times or if it would have an impact at all.

1 Comment   [ - ] Hide Comment


  • Just remember that when exporting the profiles, child profiles are NOT exported as part of the parent, each profile must be exported individually - we lost a bunch of elements because we rebuilt our server and had only exported the top-level profiles thinking all the sub-profiles would be exported as well.
Please log in to comment

Answer this question or Comment on this question for clarity



We strongly advise to build up a profile hierarchy structure. Best practice is to create a profile with the name of the company as an entry and there to store all settings which affect the entire company.
Then a child profile infrastructure with each child to create profiles of different locations.
As another child profile structure then create the departments.
A clean Profilhierachie simplifying the search and improves the quality of the structure.

We synchronize the profile structure like the ADS tree.

Answered 07/03/2013 by: scriptlogic.de
Yellow Belt

Please log in to comment