Each profile has its own settings, e.g. what the source/left directory is. However, in some cases you may want to share settings between several profiles. For example, you'll probably have the profiles log files emailed to the same email account. Instead of setting the email connection details for each profile it would be simpler to just set it once and then have those profiles use that one set of settings. That way, if the email login password changes (for example) then you only need to change it in one place instead of in each profile.
You can share the settings on the following profile settings pages:
•Variables (both for group and non-group profiles)
Creating New Shared Settings
To create new shared settings simply click the New button (in the Shared Settings box) and enter the unique name you wish to use for the shared settings, e.g. My FTP Server. Note that if you've made changes to the settings on the current settings page then they will be lost unless you apply (save) them first.
Copying Shared Settings
To copy existing shared settings simply create some new shared settings. The existing settings will be copied to the new shared settings.
Deleting Shared Settings
To delete existing shared settings simply click the Delete button (in the Shared Settings box) and choose the settings to delete. Note that you cannot delete shared settings that are being used, or shared settings that are set to be the default values.
Renaming Shared Settings
To rename existing shared settings simply click the Rename button (in the Shared Settings box) and enter the new name to use. Shared settings names must be unique, and also cannot use the name None. Renaming shared settings does not affect which profiles are using the shared settings.
Shared settings are not password protected, but profiles can be. You should be aware that if you have a password protected profile that is using shared settings, and another profile that is not password protected and using the same shared settings, then a user could change those shared settings via the unprotected profile.
An exported (or backed-up) copy of a profile will include a copy of any Shared Settings the profile is configured to use. If you re-Import such a profile, it will also import any Shared Settings configuration data as of the date of the Export. If you have made any edits to those particular Shared Settings in the meantime, those recent edits will be lost (overwritten) by the older set stored in the copy profile you just Imported. This is an inevitable consequence of storing those details on Export (but if those details were not stored, then an Import into a new system would be trying to reference Shared Settings that the backup copy does not include).
If you are using cloud services like Dropbox, or GMail, then you should use linked cloud accounts. If you are using cloud services that require a username and password, e.g. Amazon S3, or email services other than GMail, or FTP, then it's highly recommended that shared settings are used.
For FTP, email and cloud services that use a username and password, it makes sense to use shared settings simply because passwords change, and if you are using shared settings then if you change your login password then you only need to update it for one of your profiles and it will be updated in all of them (that use the same shared setting).
For cloud it is especially important to use linked cloud accounts because of the way the security systems work. With cloud services you usually don't connect using a username and password. You need to login to your cloud account (using a browser) and then give permission to the application (like SyncBackPro) to use the cloud service. This means the application does not have your cloud username and password but instead gets a special token. The application uses this token to access your cloud files. This token can be revoked by you so stopping that application from accessing your cloud account. These tokens can also expire and need to be refreshed by the application periodically. Because of this using linked cloud accounts for cloud profiles ensures that all your profiles (using the same cloud account) will share that same token. When that token is refreshed then all the profiles will use that new token.
With some cloud services, e.g. Box, this is critically important because each application is only allowed one token. So if you have two Box profiles, and are not using a linked account, then if one of the profiles has to refresh the token then it will have a valid token while the other profile will now be using an old and now invalid token. When that profile runs it will need to authorize itself again, which now stops the other profile from working. However, if both profiles are using the same linked account then they'll always be using the correct token.
All Content: 2BrightSparks Pte Ltd © 2003-2017