Royal TS automatically creates backups but there is no interface in the application to restore backups of the application configuration. One use case would be when setting up a standard configuration for a team to use, those settings can be backed up to have the file that individual team members can restore from their local Royal TS to simplify setup. Ideally this would include application settings, defaults, plugin settings.
To pre-configure the application settings, we have a sample script here:
which shows how to setup the default settings using a powershell script.
Most settings are documented here:
You can also set up the default settings for the connection types in the script.
As for the plugin settings, there's no API but these are simple XML files stored in %appdata%\code4ward\<<plugin-id>>\plugin.config
Pre-deploying them to the profile directory using a logon script, for example should be no problem.
Let me know if this helps.
Just to be clear, we are using shared documents (in Royal Server), so the main concern here is the application settings, default settings, and plugin settings. So we are using things like Named Credentials as mentioned in the provided link.
The potential duplicate IDs was a concern. At some point when I have time, I want to write a script that would take a config file that is configured with all the settings that we documented on our wiki, and put it in place where that config lives for that user so they don't have to step through all the settings and make the suggested changes. Part of that would involve figuring out if I should be generating new IDs and replacing them in their copy of the config. My suggestion here would be if the app could provide an interface to do that, where a config backup could be restored, and perhaps optionally have it generate new IDs automatically. In that case it may need to strip out open documents, if a backup from another person was used.
the document backup is intended as a safety net in case a file gets corrupt. It may be dangerous to use those files for other users, especially when assets are shared because of potential duplicate IDs. I guess your other feature request (doc templates) is another similar to what you are trying to do here, correct?
Many users are using our team-sharing functionality and keep a central configuration of connections and tasks while each team member has their own set of credentials: