Skip to content

Required user rights for the server system

User rights for installation and updates

To install a versiondog server, the user who executes the Setup.exe file must have local administrative rights and start the setup with these rights: Right-click on the Setup.exe file and select Run as Administrator.

This administrator user must have full access to all directories in which the server archive and the remote server archive are located.

For security reasons, some services are started with reduced privileges during installation and productive operation of the system. It is therefore necessary to define a standard user before installation who has read and execute access rights for the installation directory (for example, C:\Program Files (x86)).

User rights for running the server

The versiondog server is usually installed as a service that runs either as the local system account or with a named user account. This does not have to be an administrator for the base system; a standard user might be sufficient.

However, with standard users there may be restrictions on the use of individual third-party editors that are used for uploads and/or comparison of certain component types. In this case, agents can also be used.

If you want to use Active Directory, LDAP, or OAUTH authentication, you must configure the service to run under a dedicated user account that has the necessary permissions to access these services. The local system account does not have sufficient rights for these integrations.

User rights for the installation directory

Standard users require access rights to read and execute the installation directory, even if the versiondog server is running under a user with administrative rights.

User rights for the local and remote server archive

The owner of the complete directory and its contents should be the user under which the versiondog server is running. This user must have full access to the directory. The default user does not necessarily have to have full access, but there must also be no rules that prevent full access for the default user.