> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/knowledge-base/how-to-articles/generate-a-script-for-database-permissions.md).

# Generate a script for database permissions

Generate an SQL script in the Devolutions Server Console to grant database permissions to the Scheduler service and web application accounts.

The following instructions provide the method to generate an SQL script to grant permissions to accounts that are used to communicate with the SQL database. The scriptsql files can be generated for the Scheduler Service account and Web Application account. For these accounts, see this knowledge base article about [Pre-Deployment Account Survey](/server/knowledge-base/knowledge-base-articles/pre-deployment-account-survey.md).

To get to this dialog:

1. From the Devolutions Server Console, edit the Devolutions Server instance.
2. Go in the ***Database*** tab.
3. Click on the ***Advanced Credentials*** button.
4. Click on the arrow beside of one of the ***Apply Least Permissions*** buttons.
5. Click on the ***Generate Script*** button to save thesql file.


---

# 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://docs.devolutions.net/server/knowledge-base/how-to-articles/generate-a-script-for-database-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.