So far every post I've read has nothing to do with Samba and everything to do with Linux file permissions.
Let's take the original post as an example ( although by this time I think the OP has moved on ).
OK, so he set up a new directory using say ... "sudo mkdir /home/test". He may have even changed ownership to his own username say ... bob : "sudo chown bob /home/test"
1. //home/test - Which I can see and access with no problems (can't write to it though even though I set the share as writable?, but, I can read from it). This is available to everyone.
That's going to create a folder owned by bob with permissions of 755. Bob can read and write and everyone else can only read. The fact that he set the samba share to allow write will not override the Linux permissions on the folder itself.
The second thing is he needs to define exactly what he means by "write". A write to a directory means to add to or delete from that directory. A write to a file means the ability to edit the contents of that file.
If he wants everyone to add or delete files from that directory then he needs to change permissions:
If he wants everyone to do the above and also be able to edit the contents of it's files then things can get a bit more complicated. If this is a peer-to-peer type of situation where bob wants to share /home/test to mary then the simplest way is to add a line to the share definition like this:
sudo chmod 0777 /home/test
"bob" is the local login user of the machine that has the /home/test share. When the guest accesses the share his/her identity will be converted to bob. Everything that mary adds to the share will save as owner = bob so everyone will be able to edit everyone else's files.
path = /home/test
read only = No
guest ok = Yes
force user = bob
In any event no one here told us what method they are using to create the Samba share. There are two methods ( Usershare - a.k.a. Nautilus-share ) and Classic-share. Their share definitions are in two different places and are handled differently. So it's always best to post the output of the following commands when asking for help:
It would have been a good idea to post the permissions on all the target folders as well so responders could assess how to change permissions to accomplish the desired requirement.
net usershare info --long
EDIT: @The Guv, your requirements are so different from the rest that it really warrants a separate post in my opinion.