> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/ipxe-ws/planning/permissions.md).

# Permissions

The [iPXE Anywhere Web Service installation wizard](https://documentation.2pintsoftware.com/ipxe-ws/installation/ipxe-anywhere-web-service-install.md) checks if the user account executing the installation has sufficient privileges to create the SQL database, but the user account does not actually create the database. The SQL database is created by the "2Pint Software iPXE Anywhere Web Service" at service startup.&#x20;

Prior to installing the iPXE Anywhere Web Service, the following permissions are required:

## Installer Account Permissions

* Local administrator rights on the server which will be hosting the iPXE Anywhere Web Service
* **dbcreator** permissions for the SQL database Instance
* **db\_datawriter** permissions for the master database

## Machine Account Permissions

After the installation wizard is complete, the "2Pint Software iPXE Anywhere Web Service" will start and attempt to connect to SQL. At service startup, the service will check for the iPXE Anywhere database, and if it does not exist it will attempt to create it. The service runs as the user context "NT AUTHORITY\SYSTEM" or the Local System Account.&#x20;

* If SQL is installed on the same machine as the iPXE Any Where Web Service, the account: NT AUTHORITY\SYSTEM must be granted **dbcreator** permissions. The service will also grant the local system account **db\_owner** permissions to the iPXE Anywhere database.&#x20;
* If SQL is installed in a remote SQL server, the Domain Machine Account (ComputerAccount$) must be granted **dbcreator** permissions. The service will also grant the domain computer account **db\_owner** permissions to the iPXE Anywhere database.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.2pintsoftware.com/ipxe-ws/planning/permissions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
