> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/ams/v2.0/help-and-support/advanced-help-topics/audit-templates.md).

# Setting up audit templates

Access Manager provides a [comprehensive set of variables](/ams/v2.0/help-and-support/advanced-help-topics/audit-variables.md) you can use in your HTML and JSON audit templates.

Access Manager uses the [Handlebars](https://handlebarsjs.com/guide/) language to allow you to insert variables into templates, and even perform conditional rendering of your template, based on the contents of the audit data.

## HTML example

In this simple example, we can see reference to the `Response.Target` attribute, and some conditional rendering based on the value of `Response.IsSuccess`.

```html
<html>
<div>
    <p>Access to {{Response.Target}} was {{#if Response.IsSuccess}}granted{{else}}denied{{/if}} for {{user.FullyQualifiedName}}</p>
</div>
</html>
```

## JSON example

In this example, we can see examples of conditional rendering of a Microsoft Teams message card, inside the summary and title elements, as well as the conditional addition of the `computer` section.

```json
{
  "@type": "MessageCard",
  "@context": "http://schema.org/extensions",
  "summary": "{{#if Response.IsSuccess}}✅ Access to a {{Response.TargetType}} was granted{{else}}❌ Access to a {{Response.TargetType}} was denied{{/if}}",
  "title": "{{#if Response.IsSuccess}}✅ Access to a {{Response.TargetType}} was granted{{else}}❌ Access to a {{Response.TargetType}} was denied{{/if}}",
  "sections": [
    {
      "text": "{{Response.message}}"
    },
    {
      "title": "Details",
      "facts": [
        {
          "name": "Requested access",
          "value": "{{Response.AccessTypeDescription}}"
        },
        {
          "name": "Name",
          "value": "{{user.DisplayName}}"
        },
        {
          "name": "User name",
          "value": "{{user.FullyQualifiedName}}"
        },
        {{#if Computer}}
        {
          "name": "Computer",
          "value": "{{computer.FullyQualifiedName}}"
        },
        {{/if}}
        {{#if Response.IsSuccess}}
        {
          "name": "Access expiry",
          "value": "{{Response.AccessExpiryDate}}"
        },
        {
          "name": "Matched rule",
          "value": "{{Response.MatchedRuleDescription}}"
        },
        {{/if}}
        {
          "name": "Request reason",
          "value": "{{Request.Reason}}"
        }
      ]
    }
  ]
}
```


---

# 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.lithnet.io/ams/v2.0/help-and-support/advanced-help-topics/audit-templates.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.