> 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/power-monitor/governanca/operacao.md).

# Operations

Governance menu group that brings together the artifact lifecycle: refresh and job schedules, deployment pipelines and their deployment history, model change history, workspace Git status and the item

The **Operations** group brings together, in the Governance menu, the screens for the artifact lifecycle: **when** they are refreshed (semantic model refresh schedules and Fabric item job schedules), **how** they reach production (deployment pipelines and deployment history), **what changed** in the structure of models, **how version control stands** for workspaces (Git) and **what disappeared** from the tenant (deleted artifacts).

Use the group to find refresh concentration times on the capacities, review the deployment pipelines and their administrators, trace who deployed what, discover breaking changes in models, find workspaces with uncommitted changes and confirm when an item stopped existing in the environment. Reading the screens is open to all profiles; creating, editing or deleting schedules and turning on the models' breaking-change alert is exclusive to **Administrators**.

## How to open

1. In the side menu, click **Governance**.
2. Click **Operations** to expand the group and choose the screen, for example *Governance › Operations › Schedules*.

The group is collapsible: clicking its name only expands or collapses the list, without changing the screen. When the open screen belongs to it, the group is already expanded. On the [Home](/en/power-monitor/pagina-inicial.md) page, each screen in the group has its own shortcut in the Governance section.

## Screens in the group

| Screen                                                                                    | What it shows                                                                                           |
| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| [Schedules](/en/power-monitor/governanca/operacao/agendamentos.md)                        | Semantic model refresh schedules and Fabric item job schedules, heat map and Refresh Execution Timeline |
| [Deployment Pipelines](/en/power-monitor/governanca/operacao/pipelines-de-implantacao.md) | The tenant's deployment pipelines, their stages and administrators, queried live in Power BI            |
| [Deployment history](/en/power-monitor/governanca/operacao/historico-de-deploys.md)       | Deployments between pipeline stages: who ran them, when, what changed and whether they worked           |
| [Model History](/en/power-monitor/governanca/operacao/historico-de-modelos.md)            | Structural changes in semantic models, with version comparison and an optional breaking-change alert    |
| [Workspace Git](/en/power-monitor/governanca/operacao/git-dos-workspaces.md)              | Workspaces connected to Git, uncommitted changes and conflicts                                          |
| [Deleted Artifacts](/en/power-monitor/governanca/operacao/artefatos-excluidos.md)         | Items that no longer exist in the tenant and the detection date                                         |

## Related pages

* [Governance](/en/power-monitor/governanca.md): overview of the module and of the menu groups
* [Infrastructure](/en/power-monitor/governanca/infraestrutura.md): capacities, gateways and connections used by the refreshes
* [Data and Engineering](/en/power-monitor/governanca/dados-e-engenharia.md): the pipelines, notebooks and other items that the schedules run


---

# 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/power-monitor/governanca/operacao.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.