> 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/concepts/readme.md). # Concepts In this section, you'll find information on a variety of concepts that are generally applicable to the Privileged Access Management (PAM) industry, as well as for concepts that are specific to StrongDM. ### What is StrongDM? Read the [What is StrongDM?](/concepts/what-is-strongdm.md) guide to get a good understanding for what StrongDM is, and what kind of problems it can be used to solve in your organization's infrastructure. ### How StrongDM Works Read the [How StrongDM Works](/concepts/how-strongdm-works.md) guide to get an overview of how StrongDM works, including the basic pieces of network infrastructure, how access is requested and provided, and how resources are managed. ### Security The [Security](/concepts/security.md) section provides a variety of security-related information for a first look by security teams who are considering their organization's use of StrongDM. StrongDM also has further security resources and information available for customers and prospects. --- # 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/concepts/readme.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.