I don't believe this is a recommended way to share access to a SVN repository. You're using the
file:/// protocol to access the repo and it's generally discouraged to do it this way. See this StackOverflow Q&A titled: svn repository on Windows network share.
From the TortoiseSVN documentation
file:// access is intended for local, single-user access only,
particularly testing and debugging. When you want to share the
repository you really need to set up a proper server, and it is not
nearly as difficult as you might think. Read the section called
“Accessing the Repository” for guidelines on choosing and setting up a
This same sentiment is echoed in the SVN Bean Book as well.
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 a 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
permission 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 it can entail all the same problems if the
administrator isn't careful.
Read through the SO Q&A. There are number of people attesting to problems they ran into, doing it this way where the repository got corrupted.
Better to setup an actual
svnserve daemon and let it control access to the repository. It's pretty simple to set this up.