> 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.md).
# Management Console
The Management Console at [management.umh.app](https://management.umh.app) is where you create UMH Core instances, configure what they do, and decide who in your company may change it. UMH Core itself runs on your own hardware. The console is the account layer around it.
## How it works together with UMH Core
```mermaid
flowchart LR
subgraph MC["Management Console (cloud)"]
ACC["Account, organization, users, licence"]
CFG["Instance configuration"]
STAT["Status, logs, metrics, topics"]
end
subgraph Site["Your site"]
CORE["UMH Core (container)"] --> UNS["Unified Namespace
(your data)"]
end
CFG -- pull --> CORE
CORE -- push --> STAT
```
An instance registers itself once, using a token you generate in the console. After that, configuration travels down and status travels up:
* You edit a bridge in the console, the console queues the change, and the instance picks it up on its own schedule.
* The instance reports health, logs, metrics, and the topic data behind the [Topic Browser](/usage/unified-namespace/topic-browser.md).
The instance opens outbound HTTPS to `management.umh.app`, and by default nothing listens for connections from the internet, see [Deployment Model](/production/security/deployment-security.md#deployment-model-edge-only-architecture). It needs that outbound connection, so UMH Core does not run air-gapped.
## Signing in
1. Go to [management.umh.app](https://management.umh.app) and enter your email address.
2. Complete the sign-in method your company uses. Which one you get depends on your account and your plan, see [Authentication](/management-console/authentication.md).
3. Create an instance, or open one that a colleague already created.
## What you manage here
| Area | Where |
| ------------------------------------------ | --------------------------------------------------------------------- |
| Instances, bridges, data models, topics | [Usage](/usage.md) |
| Sign-in methods | [Authentication](/management-console/authentication.md) |
| Roles, locations, emergency access | [Users and Permissions](/management-console/users-and-permissions.md) |
| Threat model, responsibilities, compliance | [Security](/management-console/security.md) |
Companies, membership, licences and editions are not documented yet. Ask your account executive in the meantime.
Everything you build with the console is documented under [Usage](/usage.md), because it works the same whether you configure it in the console or by editing the instance's config file.
## Account and settings
Open the account menu at the bottom of the sidebar, then **Settings**, for three tabs:
* **Account** shows your name, email, company, and licence state.
* **Settings** holds **Advanced Mode**, which reveals options for power users, and **Early Access Features**, which switches on features that are still being finished. Early access features can change or break without notice.
* **Permissions** (only available for Enterprise) shows your current role and what it allows, see [Users and Permissions](/management-console/users-and-permissions.md).
---
# 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.md?ask=&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.