> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/access/on-premise/login-on-on-premise.md).

# Login on On Premise

## Login – Accessing Your Account <a href="#login--accessing-your-account" id="login--accessing-your-account"></a>

Your available sign-in methods depend on your account and the [Environment Settings](https://docs.decisionrules.io/doc/environment/environment-settings).

#### Email and password <a href="#email-and-password" id="email-and-password"></a>

1. Enter your email and password.
2. If 2FA is enabled, enter the current code from your authenticator app and select **Continue**.
3. If the environment requires 2FA and you have not set it up, follow **Set up two-factor authentication** before accessing the application.

See [Two-factor authentication](https://docs.decisionrules.io/doc/profile/two-factor-authentication-2fa) for setup and troubleshooting.

{% hint style="warning" %}
When **Only SSO** is enabled, standard users must use Environment SSO. Environment Managers and License Owners can still sign in with their email and password, subject to the environment's 2FA and email-domain settings.
{% endhint %}

#### Single Sign-On (SSO) <a href="#single-sign-on-sso" id="single-sign-on-sso"></a>

Select **Sign in with SSO**. On Docker / On-Premise:

| Configuration                                           | What happens                                                |
| ------------------------------------------------------- | ----------------------------------------------------------- |
| One SSO provider is configured in the application       | You are redirected to that identity provider.               |
| Several SSO providers are configured in the application | The SSO form opens so you can select the intended provider. |

On the SSO form:

* Enter the **SSO Name** provided by your organization administrator to use organization SSO.
* Leave **SSO Name** blank to use environment SSO configured in **Environment → Settings**.

Complete sign-in at your identity provider. DecisionRules then returns you to the application without asking for a separate DecisionRules 2FA code.

If the provider name is incorrect or the selected configuration is unavailable, check the name with your administrator.

{% hint style="info" %}
Administrators can configure [environment SSO](https://docs.decisionrules.io/doc/environment/environment-settings#configure-environment-sso) or [organization SSO](https://docs.decisionrules.io/doc/organization/settings#single-sign-on-sso).
{% endhint %}

#### If an image verification appears <a href="#if-an-image-verification-appears" id="if-an-image-verification-appears"></a>

An authentication form may show an image CAPTCHA when additional verification is needed or the usual verification service is unavailable. Enter the characters shown and submit the form again. If a new image appears after an unsuccessful attempt, enter the characters from that image.

Once authentication and any required 2FA are complete, you can access your workspace.

<figure><img src="https://437457296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MN4F4-qybg8XDATvios%2Fuploads%2FYxENEXFiQ8GpzjkiRlJq%2Fon_prem_login.png?alt=media&amp;token=116747e2-1f81-4857-98ef-8860604cc8e6" alt=""><figcaption></figcaption></figure>


---

# 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.decisionrules.io/doc/access/on-premise/login-on-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.