# Sign Up on On Premise
### Sign up in on-premise installations
This page describes how user registration works in self-hosted (on-premise) installations of DecisionRules.
The sign-up process depends on whether the application is already running with existing users, or whether it is a brand-new installation with no registered users yet.
### Existing installation
If the Decision Rules application is already running and at least one user is registered, the sign-up process works the same way as in the Cloud version.
Users can register through the registration form available on the login page. After completing registration, the user can sign in and access the application according to assigned invitations and roles.
No email verification is required unless explicitly configured by your organization.
### Initial registration (first user)
When Decision Rules is deployed for the first time and no users exist yet, the first registered user plays a special role.
In this case, the first user must be registered by one of the **license owners**.
The initial registration establishes the first administrative access to the application and allows further configuration, including inviting additional users and managing access.
Once the first user is registered, the application switches to the standard sign-up behavior used for existing installations.
***
### Important notes
* Only one initial registration is possible when the system has no users.
* The first registered user should always be a license owner.
* After the initial setup is completed, all further registrations follow the standard sign-up flow.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.decisionrules.io/doc/access/on-premise/sign-up-on-on-premise.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.