> For the complete documentation index, see [llms.txt](https://docs.powermonitor.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powermonitor.com.br/en/perguntas-frequentes/duvidas-tecnicas/atualizacoes-do-sistema.md).

# System updates

How Power Monitor updates reach you and how to suggest improvements.

Power Monitor is continuously updated by the Power Tuning team. Because it is a **100% SaaS** solution, updates are applied to the platform, with no action required on your side.

### Do I need to install any update?

No. When you open the portal, you are already using the latest version, including in the app installed on your phone's home screen. If the browser has had a tab open for a long time during an update, just reload the page.

### What about the application in my tenant?

The application (Service Principal) registered in your Entra ID does not need to be updated. When a new feature depends on an **additional permission**, it appears as pending in **Settings › Additional Permissions**, and an administrator decides whether to grant it.

### Will I be notified about new features?

Yes. The Terms of Use provide that relevant changes affecting the use of the platform are communicated. Power Tuning also announces what is new on:

* **Power Tuning LinkedIn:** [powertuning.com.br/linkedin](https://powertuning.com.br/linkedin)
* **Power Tuning YouTube:** [powertuning.com.br/youtube](https://powertuning.com.br/youtube)

### Can updates interrupt monitoring?

Updates are designed to have minimal impact. The checks on your environment run in regular cycles and resume automatically. The platform's availability commitment is **99%**, according to the Terms of Use.

### Can I request new features?

Yes. Open a ticket in **Support**, inside Power Monitor, contact us on [WhatsApp](https://powermonitor.com.br/whatsapp), or [schedule a conversation with our team](https://powermonitor.com.br/apresentacao).


---

# 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.powermonitor.com.br/en/perguntas-frequentes/duvidas-tecnicas/atualizacoes-do-sistema.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.
