The most simple setup is to have the OneScript Client connect directly to the OneScript SQL Server database using Windows authentication, but there are other options. You can have the OneScript Client connect to the OneScript webservice that then connects to the database. Instead of Windows authentication a username and password setup is possible. Or you could have a mixture of setups where your internal users connect directly to the database using Windows authentication and external users connect through the webservice using a username and password.
After entering you license and activating your OneScript Client you should be on a page that prompts you for a database connection string and includes a link to open the OneScript.sql file.
Create a new SQL Server database named OneScript (or anything).
Open the OneScript.sql script in SQL Server Management studio. Change to the new database (USE OneScript). Execute the SQL to create the database objects.
If the OneScript Clients or the (optional) OneScript webservice will be connecting to this database using a SQL Server user account (as apposed to Window's authentication), then create the SQL Server user account now and give it rights to the database you created earlier. It can be called anything you want, it will be used in the connection strings of the OneScript Clients or the OneScript webservice. Note the name and password because they will be entered into the clients.
Continue editing the server information by entering a name, this can be anything you want. You can have the OneScript Client connect to more than one OneScript Server, so each connection needs to be named something unique and should be descriptive. In naming a connection also note that a OneScript database can have multiple projects.
Next select the Server Type. This will be Database or Webservice depending on your setup.
Next you will enter either a database connection string or the URL to the webservice. Edit the defaults as needed. So you will end up with something similar to one of the following 3:
Server=myServerAddress;Database=myDataBase;User Id=myUsername; Password=myPassword;
The examples above are a SQL Server connection string using Windows authentication, a SQL Server connection string using username/password, and the URL to the OneScript webservice that you installed on your server.
User authentication is selected next and has nothing to do with the previous step where you defined how the OneScript Client connected to the OneScript Server. It is saying how your users will authenticate within the OneScript application. You have the choice of either Windows Authentication or username/password. If all the users are on the same internal Windows domain then it is easier to use Windows Authentication.
Next, test the connection and save the information if successful.