---
title: User Account Requirements
slug: blueprint/user-account-requirements
createdAt: 2023-03-21T23:22:12.000Z
---

The following diagram illustrates the user account requirements for Blueprint installation and ongoing operation.

![](https://api.archbee.com/api/optimize/HRPaq4oJ2h9pHAfcjJGa6/8rjfPwMgVopi7ZEaU2xM1_useraccountrequirements.png)

# Blueprint Server User

This user represents a service account that is used to run Blueprint's different components and facilitate communication between them for the application's regular operations. This user is used The following requirements must be met for this user:

- The user account must be either a domain user (e.g. ACMECORP\Blueprint) or a local server account (e.g. ApplicationPoolIdenity).
- The user account must exist on both the web application and database servers.
- The user account can have standard user privileges and does not need to be an administrator, but will automatically be granted read and write permissions to Blueprint's application and logging directories.

# Windows Local Administrator

This user represents a Windows account that has local administrator privileges on the web application server. This user account is used to install the Blueprint application and configure the system. It can be either a local or domain account and is only needed during software installation.

# Database System Administrator

This user represents an account within Microsoft SQL Server that has "sysadmin" permissions. This user must have administrative privileges so that it can create the necessary resources in SQL Server. This may be either a Windows or SQL user account and its credentials will need to be supplied to the Bluerpint installer during the installation process. Similarly to the Windows Local Administrator account, this is also only needed during software installation.