Theoretically, you can have manage multiple projects in sub-folders of a single repository, and then just provide the URLs to the specific folder for each project to your users. However, we generally recommend creating a separate repository for each project. This is more secure, and if anything ever happens to the repository then it only affects one project, not all of them.
Setting up the repository on your SVN server
This is generally a task for the system administrator, who should take the time to familiarize themselves with the management of their SVN server software. If you have an SVN hosting provider, they will provide tools for doing this task. We currently recommend the Visual SVN distribution, which is free for commercial use for up to 15 users and provides easily configurable and secure local and remote access via https://.
Choosing your repository structure – branching considerations
If you are only going to host a single HM project in each repository and not do any branching, you can just create an empty repository folder and load your HM project into it directly. If you don't know what branching is, this is what you should do.
If you do plan on doing branching, then you will already know how you want to set this up. Note that branching is not supported from within Help+Manual. You will need to set up the branching yourself and then have your users check out and synchronize working copies of the branch they should be working on.
Get the URL for your users — local and remote access
Once you have set up the repository you will need the URL for you and your users to be able to access the repository and synchronize with it. This URL will generally be provided by your SVN server software, for example Visual SVN.