## Permission for installing Leapwork (Studio, Controller or Agent)

You must have full administrative access to the Windows computer you wish to install or upgrade Leapwork on. Full administrative privileges are essential because installation requires access to the Windows registry and Windows System folders.

If you are trying to install software on a computer in a corporate or networked Windows environment but do not have the necessary privileges, you will need to contact your system administrator to install the software for you. These rights are not required to run Leapwork once it is properly installed.

## SQL Database Permission Required to Setup the Enterprise Edition

As a first step, Leapwork creates a database and tables in MS-SQL after connecting to it, so it's essential to use an MS-SQL server during the installation phase.

To access & manage SQL infrastructure download [SQL Server Management Studio (SSMS)](https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15). SSMS provides tools to configure, monitor, and administer instances of SQL Server and databases.

The database user must have the **dbcreator** role in MS-SQL. Members of the **dbcreator** fixed server role can create, alter, drop, and restore any database.

_**Please note : MS SQL Server 2016 (version 13), 2017 (version 14), 2019 (version 15), 2022 (version 16), and Azure SQL are supported.**_

Once the database and tables are created and/or migration is completed, **dbcreator** access from the MS-SQL server can be removed.

**Leapwork Enterprise installation**, for SQL Server the **dbcreator is highly privileged permission and database administrators in an organization will often be reluctant to give this permission.**

**In this scenario,** the below approach can be used where the dbcreator role is not required.

The SQL Server database administrator can create the two blank databases (e.g., Assets & Report) and grant the **db_owner** access to SQL user created to use during Leapwork installation to connect the databases.

**Steps to create blank databases.**

**Step 1** - Open **SQL SSMS** (SQL Server Management Studio)

**Step 2** - Go to **Databases** > right-click > **New Database**.

**Step 3** - **Name** the **Database** and select the **Owner** (the SQL user created for Leapwork) for the database.

If the owner is not selected in the above step, later **db_owner** **role** can also be mapped from SSMS (SQL Server Management Studio)

**Step 1** – Open **SSMS**  
**Step 2** - Go to **Security** – **Login** s – **User**  
**Step 3** - Right-click on the user – **Properties**, and map the **db_owner role** to the databases created as shown in the below image.

We can also use the below **SQL Query in SSMS** for creating a database & assigning the **db_owner** role.

|     |
| --- |
| create login username with password = 'Password'<br>go<br>create database Report<br>go<br>use Report<br>go<br>create user username for login username;<br>go<br>EXEC sp_addrolemember 'db_owner', 'username'<br>go<br>create database Asset<br>go<br>use Asset<br>go<br>create user username for login username;<br>go<br>EXEC sp_addrolemember 'db_owner', 'username'<br>go |

If you do not want to assign the **db_owner role**, for Leapwork to work minimum access that is required is **db_datareader** and **db_datawriter.** Please ensure **db_denydatareader** and **db_denydatawriter** is unchecked.

**If you require further clarification, please contact our [Priority Support](mailto:prioritysupport@leapwork.com).**
