> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/getting-started/setup/create-a-user.md).

# Create a user

**User** is the third step of the wizard. The account you create here is the first administrator of the management console, and the one you use to log in for the first time.

Fill in **Username**, **Password** and **Password confirmation**. The two passwords have to match, or the wizard reports **Passwords do not match**. On success you see **User is created successfully**.

{% hint style="info" %}
Your password needs at least 12 characters, including an upper-case letter, a lower-case letter, a number and a special character.
{% endhint %}

Write the credentials down. You can change the password later from the management console, or from the **User** page of the configuration panel.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-498fe9353002274b22bb917515eb5429a3510fee%2Fimage%20(34).png?alt=media" alt=""><figcaption></figcaption></figure>

Upgrading from version 2? An administrator already exists, so you can press **Skip** on this step.


---

# 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.infotopics.com/getting-started/setup/create-a-user.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.
