> For the complete documentation index, see [llms.txt](https://docs.guardware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardware.com/data-governance/introduction.md). # Introduction {% embed url="" %} GuardWare uses data governance settings to define what sensitive data to detect, how to classify it, and who to notify when it is detected. Data types define the detection rules. Classifications set the sensitivity level. Data owners assign responsibility and receive alerts when GuardWare finds their assigned data. Set up these components before you run broad scans or build new policies. A clear structure improves detection quality, speeds up triage, and helps the right people respond faster. ### Recommended setup order 1. Create your data classifications. Start from the least sensitive and move upward. 2. Create your data owners. Add the people who should receive alerts. 3. Create or review your data types. Assign each one a classification and an owner. This order keeps your detection rules organised from the start. It also avoids rework when you begin assigning owners and classifications to new data types. ### Quick links * [Data Classification](/data-governance/data-governance/data-classification.md) - define sensitivity levels for detected content * [Data Owner](/data-governance/data-governance/data-owner.md) - assign responsibility and alert recipients * [Data Type](/data-governance/data-governance/data-type.md) - create the detection rules GuardWare uses during scans --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.guardware.com/data-governance/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.