Chapter 6 of the Subversion Book (http://svnbook.red-bean.com/nightly/en/svn- book.html#svn.serverconfig) deals with the server. I found this paragraph: "Do not be seduced by the simple idea of having all of your users access a repository directly via file:// URLs. Even if the repository is readily available to everyone via network share, this is a bad idea. It removes any layers of protection between the users and the repository: users can accidentally (or intentionally) corrupt the repository database, it becomes hard to take the repository offline for inspection or upgrade, and it can lead to a mess of file- permissions problems (see the section called "Supporting Multiple Repository Access Methods".) Note that this is also one of the reasons we warn against accessing repositories via svn+ssh:// URLs - from a security standpoint, it's effectively the same as local users accessing via file://, and can entail all the same problems if the administrator isn't careful." Let me say I am not advocating using the server, just trying to better understand. I *have* experienced the permission issues they mention, but I can't say the permission vulnerabilities have caused a problem with the small trusted teams I work with at work, nor would I have a problem using this mode with our small team here. Having said that, I'll look into setting up the server mode. The one thing that might give us read-only web access which might be useful. Tim