> For the complete documentation index, see [llms.txt](https://docs.myrspoven.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myrspoven.com/customer-interfaces/myportal.md).

# myPortal

myPortal is the customer-facing web application for monitoring building performance under myCoreAI. It surfaces energy use, indoor climate, optimization activity, and reported savings across a single building or an entire portfolio.

## Audiences

| Role                               | Primary use                                                                                                         |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Building owners and asset managers | Portfolio-level view of energy, savings, and indoor conditions                                                      |
| Technical operations               | Per-building drill-down into HVAC systems and the setpoints myCoreAI writes to the Building Management System (BMS) |
| Sustainability and reporting staff | Energy and savings exports for internal or external reporting, including alignment with ISO 50001 reporting cycles  |

Access is per user. Permissions are managed by Myrspoven.

## Views

* **Portfolio dashboard** — recent energy use, indoor climate status, and flagged issues across accessible buildings.
* **Building view** — drill-down into a single building, its systems (heating, ventilation, cooling), and individual signals.
* **Graphs and history** — time-series for energy consumption, indoor temperature, and tracked signals. Date range and resolution are adjustable.
* **Reports** — measured energy use versus baseline, with estimated savings over a selected window. Reporting fidelity depends on energy-data resolution — see [Energy data](/integrations/overview/energy-data.md).
* **Alerts and flags** — surfaced in-app when myCoreAI or the data pipeline detects a missing signal, stuck sensor, or similar fault.

## Capabilities

* **Monitor** — current and historical energy use, indoor climate, and the setpoints myCoreAI is sending to the BMS.
* **Compare** — measured consumption against agreed baselines over arbitrary windows.
* **Upload data** — manual energy-data upload where automated transfer is not available. See [Energy data — Manual upload](/integrations/overview/energy-data/manual-upload.md).
* **Configure (limited)** — selected settings such as comfort bounds and occupancy schedules, where the contract permits. Deeper configuration changes are made by Myrspoven.

{% file src="/files/BUzps7kGQEBt8sgGD6ny" %}

## Access

Browser-based; no installation. Customers receive an invitation email with a sign-in link at onboarding. Additional users are requested through Myrspoven.

{% file src="/files/AZO2cb8yRIwxmasXbb1w" %}

## Browser support

Recent versions of Chrome, Edge, Firefox, and Safari. Mobile browsers cover most read-only views; configuration tasks require desktop.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.myrspoven.com/customer-interfaces/myportal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.