Thank you for your quick response. I am not sure I agree about the "more convenient" comment, but I have returned to version 1.4.103 to try out your suggestions on two of my computers. Let's call them "A" and "B". On both computers I set the folder_defaults.use_tracker and folder_defaults.use_relay to *false*. On "A" I used Add folder to create a new Sync folder. As expected the Tracker and Realy Preferences were turned off. I then tried the three following experiments. (1) I first used Share to email a share-link to "B", just using the default settings. I succeeded in linking the folder on "A" and "B". However, the Preferences for the folder on "B" still showed the normal defaults of using both Relay and Tracker. In other words, the folder created by the Share link did not use the global default settings. (2) On "B", after disconnecting and deleting the new folder, I used Add Folder to create a new folder, knowing that it would initially have its own and different full access secret. This folder now had the correct setting for Tracker and Relay. Then I tried to Update the key for this folder with a read only key from "A", but was told that I could only use a full access key when updating the key. Feels a bit like a bug to me, since to me, it would be surely useful to replace a full access key with a read only key at times. (3) Finally, on "B", I disconnected and deleted the folder just created. I then went to the global Preferences menu and selected Enter a key.... Using the read only key from "A" I was able to create a new folder on "B" in my selected location, with the correct Preferences setting and read only secret. from "A". FINALLY SUCCESS!! As a comment, I really think that the global Preferences menu is a really strange place for this functionality. On the way, I encountered these bugs and anomalies. (A) When using Share, you have the option to turn off the need for approval of peer connections. If you do, the target computer still says that confirmation is needed, but the source computer doesn't seem to respond to this. A bug, surely? ( When using Share, I tried to override the default location for the shared folder, but ran into cases where Sync garbled the name of the folder by adding something like 'undefinedName' to the actual 'Name'. Also looks like a bug to me. So, using the method in (3) above (which still seems like a clumsy work-around to me), I will now stay with Sync version 1.4 and abandon version 1.3.