Another question to answer is: Do you need strict access control below repositories?
In Subversion you can always undo each and every change a developer makes. So as long as you only allow your developers acces to the repository you can handle the rest of the security via policy.
This won't work in cases with external contracters, but if all developers are normal employees, in many cases there is no need to restrict access.
Im my eyes the time to configure every directory tree every time is much more costly than to fix a possible deletion/breakage later. (Giving access to a repository is uncommon; a new directory very common).
That leaves the tracking of changes; and I usually use AnkhSVN and TortoiseSVN for that. (Easier to maintain than most web tools and very easy to install.. You probably have them already).
Then you only need some issue tracker...