Inspired by this thread might it be worth adding a warning to the sync setup of a "child" profile if it notices it has the same sync target config as the parent?
i.e. it checks ../settings.json on save to see if it has the same sync.target and its associated fields which should be unique e.g. sync.5.path and sync.5.username then throws a error or asks the user to confirm they want to do this - that they need to have a separate target if they want to maintain a separate profile.
1 Like