> For the complete documentation index, see [llms.txt](https://docs.cerrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cerrix.com/introduction-to-cerrix.md). # Introduction to CERRIX
Welcome to CERRIX, your comprehensive solution for Governance, Risk, and Compliance (GRC) management. This documentation will provide you with an understanding of how to use CERRIX effectively. {% hint style="info" %} This documentation is still a work in progress and does not cover all functionalities of the CERRIX product yet. The CERRIX team is working on bringing new content into this documentation on a continuous basis. {% endhint %} ### Overview CERRIX is a cloud-based platform that centralizes and streamlines compliance, risk management, and audit processes. By integrating all four lines of governance, it ensures consistent workflows and enhanced operational efficiency. ### Why Use CERRIX? * **Simplifies GRC Management**: Tracks human processes across your organization. * **Improves Compliance**: Helps meet regulatory and organizational frameworks. * **Enhances Efficiency**: Reduces time and resources spent on manual processes. > **Tip**: Use CERRIX to reduce complexity and bring clarity to your compliance workflows. *** Ready to get started? Proceed to the [Getting Started](/cerrix-functionalities/getting-started.md) page for instructions on logging in and navigating the dashboard. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.cerrix.com/introduction-to-cerrix.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 `build a script that syncs our docs to a CMS` 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.