# Folderslave option
**URL:** https://forum.syncthing.net/t/folderslave-option/5819
**Category:** Feature
**Created:** [October 3, 2015, 10:47am UTC](https://forum.syncthing.net/t/folderslave-option/5819 "2015-10-03T10:47:11Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@David\_K\_Levine](https://forum.syncthing.net/u/David_K_Levine)
#### Post date: [October 3, 2015, 10:47am UTC](https://forum.syncthing.net/t/folderslave-option/5819/1 "2015-10-03T10:47:11Z")
The foldermaster feature is useful but it does not allow several machines to receive updates from each other while other “unreliable” machines may receive updates without being able to change files on the “reliable” machines. How about adding an option for Folderslave meaning that the folder can receive changes but not send them?
---
### Author:  [@wweich](https://forum.syncthing.net/u/wweich)
#### Post date: [October 3, 2015, 10:55am UTC](https://forum.syncthing.net/t/folderslave-option/5819/2 "2015-10-03T10:55:05Z")
This feature has been requested several times before; e.g.:
> [@How to set certain nodes as \[read only, backup, slave\]?](https://forum.syncthing.net/t/how-to-set-certain-nodes-as-read-only-backup-slave/899):
>
> I have a couple machines which are accessed by other individuals. While I do want all machines to receive all changes, I do NOT want any changes made on these specific machines to filter back to the rest of the nodes. A “backup TO here” scenario. How can I do this?
and has an issue on github:
>
>
> I.e. ones that we never accept updates from, but who can otherwise participate i…n the exchange as usual. Needs #63 to work securely.
I don’t know the current status of the implementation though.