> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/governance-and-monitoring.md).

# Governance & Monitoring

Governance & Monitoring covers the system-level settings and controls needed to operate BuildingPro Suites in a stable, traceable, and compliant way.

This area of Platform Core focuses on the ongoing administration of the platform itself: system configuration, auditability, and license status. It helps ensure that the platform remains secure, transparent, and operational over time.

## What You Can Manage Here

This section includes:

* [System](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/governance-and-monitoring/system.md) for central system settings and technical behavior
* [Audit Trail](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/governance-and-monitoring/audit-trail.md) for reviewing tracked system actions
* [License](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/governance-and-monitoring/license.md) for checking license details and status

## Why It Matters

Governance & Monitoring gives administrators the visibility and control required to run BuildingPro Suites as a managed platform rather than just a collection of features. It supports operational reliability, accountability, and controlled lifecycle management across the system.


---

# 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.buildings.ability.abb/collection/mandatory-base/platform-core/governance-and-monitoring.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.
