> 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/principais-funcionalidades/inventario-e-governanca.md). # Inventory and Governance Complete, up-to-date tenant inventory, with governance metadata, selection of monitored workspaces, deleted artifacts, bulk actions and exports. Power Monitor maintains a **complete inventory, updated daily**, of the items in your Microsoft Fabric and Power BI tenant, organized in the **Governance** area, with governance metadata and bulk actions for management and compliance. ## What is in the inventory | Screen or group (Governance ›) | Content | | -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Workspaces** | Collaborative workspaces, capacity, domain, state and selection of which ones are monitored | | **Semantic Models** | Semantic models and their metadata | | **Storage** | Lakehouses, warehouses and other storage items, with query analysis for SQL endpoints | | **Reports** (group) | Reports, paginated reports, dashboards, KQL dashboards, apps, explorations and metric sets | | **Data and Engineering** (group) | Mirrored databases (Fabric Mirroring) and the Fabric data engineering (notebooks, pipelines, dataflows), data science (ML models and experiments), development and real-time (eventstreams, eventhouses) items | | **Infrastructure** (group) | Capacities, gateways, connections and Azure Quotas: the tenant-level resources | | **Operations** (group) | Schedules (heat map and timeline of refreshes), deployment pipelines, deployment history, model history, workspace Git status and deleted artifacts, with the date on which Power Monitor detected the deletion | | **Compliance** (group) | **Public links** (publish to web), organization-wide links, labels and certification, naming conventions, personal data discovery, privacy risks, compliance posture, departed owners and access reviews | | **Tenant** (group) | Tenant settings, Power BI licenses and Fabric domains with their workspaces | The inventory is updated by the **automatic daily scan** and by on-demand scans in **Mapping › Inventory › Inventory** (administrators). Item screens show only items from **monitored workspaces**. ## Governance metadata and bulk actions Administrators can record governance information that does not exist in Power BI: * **Responsible person** and **Business Area Responsible** (name and email); * **Criticality Level** (Low, Medium, High, Critical or Unclassified); * **Area** and **Sub-Area**. The **Bulk edit governance** action, in **Workspaces** and **Semantic Models**, applies these fields to several items at once (only the checked fields are changed), including all items in a workspace. Also in bulk, in the **Workspace Monitoring** modal (**Workspaces** screen), you can **Enable Monitoring** or **Disable Monitoring** for the selected workspaces, and in **Mapping › Inventory › Inventory**, start a scan of only the chosen workspaces (**Start Full Scan › Select Workspaces**). {% hint style="warning" %} Disabling monitoring for a workspace removes its items from the screens, alerts and billing starting with the next measurement. See [What counts as an artifact?](/en/perguntas-frequentes/licenciamento/o-que-e-contado-como-artefato.md) {% endhint %} ## Exports * Screen tables offer **CSV export** (with an encoding that Excel opens correctly, including accented characters) and, on several audit screens, **JSON** as well, with all records that match the filter. * Dashboards can be exported as **PNG** and **PDF** (screen capture). * In **Governance › Reports**, reports can be exported to **PowerPoint** or **PDF** using Power BI's own export. * Data lineage can be exported as an image (PNG) or JSON. ## What it is for * **IT audits:** knowing exactly which items exist, where they are and who is responsible; * **Compliance (LGPD):** finding public links, critical items and where data is exposed (see **Data Quality › Data Exposure**); * **Cleanup and consolidation:** finding unused, duplicated or abandoned items; * **Planning:** tracking the growth of the environment and its distribution by capacity and domain. ## Related pages * [Governance](/en/power-monitor/governanca.md) * [Workspaces](/en/power-monitor/governanca/workspaces.md) * [Mapping](/en/power-monitor/mapeamento.md) * [Data Quality](/en/power-monitor/qualidade-de-dados.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.powermonitor.com.br/en/principais-funcionalidades/inventario-e-governanca.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.