> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/admin/audit.md). # Audit StrongDM provides a variety of tools with which to audit both the administration of your StrongDM organization itself as well as the actions of users connecting to your resources. * [Logs](/admin/audit/logs.md) can be used to monitor administrative activities as well as specific queries sent by users connecting to resources through StrongDM. Logs can be configured to be accessed through the Admin UI, through the CLI, locally on each network node, or they can be streamed to Amazon S3. * [Reports](/admin/audit/reports.md) provide overviews for the various personas who may be interested in things like license utilization and user activity, reports on access workflows and standing privileges, and executive level reports for information at a glance. --- # 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.strongdm.com/admin/audit.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.