> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/system-administration/command-line-scripts/create-first-admin-user.md).

# Create (First) Admin User

By default, a new company created from command line does not have any users configured. The first user must be created from the command line by a system administrator. Any subsequent user can be created by an authorized admin user via the browser based Access-Management Tool.

System administrators can create (first) admin user in an existing LogicNets installation using the following steps. If the company already has a

1. Open a system command prompt.
2. Type **cd /system/scripts**.
3. Type **adduser**
4. Fill in all user details
5. By default, no default applications and tools are assigned to the admin user. This step will assign all default components to all admins in all local companies
   * Go to the components folder in the unzipped LogicNets installation package and run **assign\_default\_components**
6. Open internet browser.
7. Enter URL: **http\:///\<company/logicnets.lns?verb=start\&code=logon**.
8. Check if the logon page is displayed.
9. Login with the new user credentials
10. Check whether all default system components can be accessed


---

# 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://community-test.logicnets.com/release-9/platform-documentation/system-administration/command-line-scripts/create-first-admin-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.