Just like @vikaskulhari just mentioned, you have the config file in a network drive which can be shared among all the machines where robots are installed and running. This helps you to change the configurations without really deploying the program to orchestrator again and again.
Are you referring to password changes here? I’m not sure why you need to have the passwords in the config file. You can simply use a Orchestrator credential asset to store the password and refer it from the config file.
Excellence is achieved by constant challenging and breaking off from your limitations. It isn’t taught or given; it begins within you. – @Lahiru.Fernando