> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/on-premise/technician-admin-accounts-for-on-premise.md).

# Technician admin accounts for On-Premise

Create unlimited technician accounts via SQL INSERT. Change login, title, and password post-creation via Admin Panel. No additional charge

## Can I have technician admin accounts for On-Premise?

Yes. To create a new technician, execute the following SQL statement in the database:

```sql
INSERT INTO google.dealers
SET parent_id=1,
    title='Tech role',
    last_name='Tech role',
    details='Tech role',
    role='dealer_support',
    paas_type=4,
    reg_date=CURDATE(),
    login='desired_login',
    `password`='9f2c8a4a10364437a3fc58376e912f673936de3b', -- ChangeMe!
    email='';
```

Change `login` to anything (for example `tech1`).

Change `title`, `last_name`, and `details` so the account is unique.

Hash in password corresponds to `ChangeMe!` password. After the query is executed, log in to the new technician account in the Admin Panel and change this password (or tell the customer to do it).

## How many technician accounts can I have? Does Navixy charge for it?

The number of technician accounts is unlimited. Create as many as you need for your tasks.

Technician accounts are free of charge.

## Why can't I change the technician's password? I don't see that option.

Your platform is probably old and hasn't been updated in a long time. The password change option was introduced in 2023, and if your instance is older than that, you need to update it.


---

# 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://navixy.com/docs/qna/on-premise/technician-admin-accounts-for-on-premise.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.