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

# Compliance

The Compliance section provides the tools your organisation needs to manage regulatory and internal policy compliance within the GLBNXT platform. From here, administrators can review a complete audit trail of platform activity and manage the full lifecycle of compliance policies.

* [**Audit Logs**](https://docs.glbnxt.com/configure-glbnxt/platform-configuration/compliance/audit-logs.md) — a chronological record of all tracked changes on your platform, with filtering, detailed event views, and pagination.
* [**Policies**](https://docs.glbnxt.com/configure-glbnxt/platform-configuration/compliance/policies.md) — create, publish, and track acceptance of compliance policies across your organisation, with document uploads, control questions, and reporting.


---

# 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.glbnxt.com/configure-glbnxt/platform-configuration/compliance.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.
