> For the complete documentation index, see [llms.txt](https://docs.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umh.app/management-console/authentication/username-and-password.md).

# Username and Password

You enter your email address and a password to sign in. Two kinds of account use this method, and they differ in where the password is stored and what else it is used for.

## Who this applies to

**Enterprise accounts** sign in with username and password by default. The password is stored by our identity provider, and the sign-in form is the [default connection](/management-console/authentication.md#which-company-you-sign-in-to) of your company's organization. Enterprise customers with the [single sign-on add-on](/management-console/authentication/enterprise-sso.md) sign in through their own identity provider instead.

**Community accounts created with a password** keep signing in with that password. The same password is also your [passphrase](/management-console/authentication/passwords-and-passphrases.md). New Community accounts use an [email code](/management-console/authentication/email-code.md).

## Signing in

1. Open the Management Console and enter your email address.
2. The console recognises which method your account uses. Enterprise accounts are sent to the sign-in form of their company's organization at our identity provider. Community accounts with a password see the password field directly.
3. Enter your password.
4. Enterprise accounts then enter their passphrase, which unlocks their access to the instances. For Community accounts with a password, the password already did this. See [Why every sign-in asks for the passphrase](/management-console/authentication/passwords-and-passphrases.md#why-every-sign-in-asks-for-the-passphrase).

Signing in on another device signs you out everywhere else. See [Sessions](/management-console/authentication/sessions.md).

## Resetting a password

Enterprise passwords are stored by our identity provider and can be reset there from the sign-in form.

For old Community accounts created with a password, the password is also the passphrase that unlocks your access to your instances, so it is handled like a passphrase: only you hold it. Keep it in your password manager. There is no way to reset your password, if you forgot it. See [Passwords and Passphrases](/management-console/authentication/passwords-and-passphrases.md#the-passphrase).


---

# 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.umh.app/management-console/authentication/username-and-password.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.